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: e7a2ed2d362a56bde8c9b91b50cfce259debff4a1679ba4ff04862db48aa3aa2
Tx prefix hash: cfbd5df5d877fdb1cdb468912f13d01ff89b1e0611fd08a207db6eca3c43f7a5
Tx public key: c5a94dffe4d7b86d1d5e3b009a7fda4dcf03b94f09fcb9e30900eec7acb1a729
| Timestamp: 1780805973 | Timestamp [UTC]: 2026-06-07 04:19:33 | Age [y:d:h:m:s]: 00:010:04:16:41 |
| Block: 6945 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1800 | RingCT/type: yes/0 |
| Extra: 01c5a94dffe4d7b86d1d5e3b009a7fda4dcf03b94f09fcb9e30900eec7acb1a729020900000001e49593ff00 | ||
1 output(s) for total of 34.731259744039 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ab57b4001a9b0d5e9803e1ec162cccac443f1f458dcfdc9c9bb73b493163061 | 34.731259744039 | 8565 of 0 | <20> |
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": 7005,
"vin": [ {
"gen": {
"height": 6945
}
}
],
"vout": [ {
"amount": 34731259744039,
"target": {
"tagged_key": {
"key": "3ab57b4001a9b0d5e9803e1ec162cccac443f1f458dcfdc9c9bb73b493163061",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 197, 169, 77, 255, 228, 215, 184, 109, 29, 94, 59, 0, 154, 127, 218, 77, 207, 3, 185, 79, 9, 252, 185, 227, 9, 0, 238, 199, 172, 177, 167, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}