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: 5e5fe468652fe28979ae8e58cc7592e4f3d8b9150e6d9766cf43b19d18c0fe96
Tx prefix hash: fe764ed13839d91d9091f472bb8bb5ca3031e671c273bfd4538f0ee261656e2d
Tx public key: 6cd5e255ee63758d15e1fb160f812b5482c0eb4fabec13a37c6bcbdcbb87759c
| Timestamp: 1780039659 | Timestamp [UTC]: 2026-05-29 07:27:39 | Age [y:d:h:m:s]: 00:010:18:08:18 |
| Block: 4272 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3614 | RingCT/type: yes/0 |
| Extra: 016cd5e255ee63758d15e1fb160f812b5482c0eb4fabec13a37c6bcbdcbb87759c02090000000326697be300 | ||
1 output(s) for total of 34.898914148210 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c1ccd7c007fd9dee63e11beb3df425625fed60119acf935b85eb5d19af97221 | 34.898914148210 | 5335 of 0 | <d9> |
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": 4332,
"vin": [ {
"gen": {
"height": 4272
}
}
],
"vout": [ {
"amount": 34898914148210,
"target": {
"tagged_key": {
"key": "0c1ccd7c007fd9dee63e11beb3df425625fed60119acf935b85eb5d19af97221",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 108, 213, 226, 85, 238, 99, 117, 141, 21, 225, 251, 22, 15, 129, 43, 84, 130, 192, 235, 79, 171, 236, 19, 163, 124, 107, 203, 220, 187, 135, 117, 156, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}