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: d19a9390a1a5cfa29137c4a3af13b285a37ed58a1fb2f1536d307fea74d8db2b
Tx prefix hash: 404d869471755c945685ca517fda6913ee17f97d751b66212354a9b93b90611f
Tx public key: 2b22db62ca32b2d92abf4bded184f6b5dfcbeead98622dd24df292530a4e6ab9
| Timestamp: 1780978643 | Timestamp [UTC]: 2026-06-09 04:17:23 | Age [y:d:h:m:s]: 00:000:10:31:32 |
| Block: 7985 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 657 | RingCT/type: yes/0 |
| Extra: 012b22db62ca32b2d92abf4bded184f6b5dfcbeead98622dd24df292530a4e6ab9020900000001e49593ff00 | ||
1 output(s) for total of 34.652633417914 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8572ca44eb064439dfb436d168f991b4500909a44624159c699c9d1bfb1fac74 | 34.652633417914 | 9901 of 0 | <42> |
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": 8045,
"vin": [ {
"gen": {
"height": 7985
}
}
],
"vout": [ {
"amount": 34652633417914,
"target": {
"tagged_key": {
"key": "8572ca44eb064439dfb436d168f991b4500909a44624159c699c9d1bfb1fac74",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 43, 34, 219, 98, 202, 50, 178, 217, 42, 191, 75, 222, 209, 132, 246, 181, 223, 203, 238, 173, 152, 98, 45, 210, 77, 242, 146, 83, 10, 78, 106, 185, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}