For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 97d0b0ddf847eef0d3e068892ec96787a3e6f106832abdb222fb93dc8de1cc58
Tx prefix hash: b41b013aeb33f1c876eca03ed94665e4d2683a9ce9939e61a4de1f83ad26dcb1
Tx public key: 1134e4c4340d3775d8fbf9458964ab0f9131fe6e9233c423e2df7e373b9d10e1
| Timestamp: 1779908688 | Timestamp [UTC]: 2026-05-27 19:04:48 | Age [y:d:h:m:s]: 00:012:06:31:09 |
| Block: 3220 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4666 | RingCT/type: yes/0 |
| Extra: 011134e4c4340d3775d8fbf9458964ab0f9131fe6e9233c423e2df7e373b9d10e102090000000126697be300 | ||
1 output(s) for total of 34.969010261333 HMNY
| stealth address | amount | amount idx | tag |
| 00: b9af540fed8112e15ff89079df62d67c8ad17d3ec4c506450832a0f7219a9b6d | 34.969010261333 | 3860 of 0 | <b2> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 3280,
"vin": [ {
"gen": {
"height": 3220
}
}
],
"vout": [ {
"amount": 34969010261333,
"target": {
"tagged_key": {
"key": "b9af540fed8112e15ff89079df62d67c8ad17d3ec4c506450832a0f7219a9b6d",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 17, 52, 228, 196, 52, 13, 55, 117, 216, 251, 249, 69, 137, 100, 171, 15, 145, 49, 254, 110, 146, 51, 196, 35, 226, 223, 126, 55, 59, 157, 16, 225, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}