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: abfbe3d99c950a796cd925d7b12ef69ff2f5c15d5351e75ae86018e0f4498d4b
Tx prefix hash: e824366d4380495c26d10a52a1255ac2312e05f9c2c85c8c185c3f97d86ec0ce
Tx public key: e3cce61da4b75b3696ec5a61cb3cb4f58704984a645c13af36dda45fa5ba6891
| Timestamp: 1780685221 | Timestamp [UTC]: 2026-06-05 18:47:01 | Age [y:d:h:m:s]: 00:003:06:48:56 |
| Block: 5378 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2508 | RingCT/type: yes/0 |
| Extra: 01e3cce61da4b75b3696ec5a61cb3cb4f58704984a645c13af36dda45fa5ba6891020900000001e49593ff00 | ||
1 output(s) for total of 34.825371453336 HMNY
| stealth address | amount | amount idx | tag |
| 00: 99009a3b778d024dafc102e33e9a89411c44e2e142fe59821ec99738ea7588e0 | 34.825371453336 | 6813 of 0 | <31> |
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": 5438,
"vin": [ {
"gen": {
"height": 5378
}
}
],
"vout": [ {
"amount": 34825371453336,
"target": {
"tagged_key": {
"key": "99009a3b778d024dafc102e33e9a89411c44e2e142fe59821ec99738ea7588e0",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 227, 204, 230, 29, 164, 183, 91, 54, 150, 236, 90, 97, 203, 60, 180, 245, 135, 4, 152, 74, 100, 92, 19, 175, 54, 221, 164, 95, 165, 186, 104, 145, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}