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: 23e90a117e8e8888950eada842a0523e60f40d1a9dbd69b809d1abd83e47a5ef
Tx prefix hash: d033f04233cae9253037e90217946d864c504ef784e3249697601d76c71d75e3
Tx public key: 4b1c885454435f33654e38bc9b9217ab97946c89b2c883d29c38697e33613d86
| Timestamp: 1780746260 | Timestamp [UTC]: 2026-06-06 11:44:20 | Age [y:d:h:m:s]: 00:002:13:02:27 |
| Block: 6456 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1430 | RingCT/type: yes/0 |
| Extra: 014b1c885454435f33654e38bc9b9217ab97946c89b2c883d29c38697e33613d86020900000001e49593ff00 | ||
1 output(s) for total of 34.753839742925 HMNY
| stealth address | amount | amount idx | tag |
| 00: 19a2d16fc3b172ce7a88f60bd3c0bc3c8a0e721dd4985be965dd5d508118e05c | 34.753839742925 | 7949 of 0 | <13> |
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": 6516,
"vin": [ {
"gen": {
"height": 6456
}
}
],
"vout": [ {
"amount": 34753839742925,
"target": {
"tagged_key": {
"key": "19a2d16fc3b172ce7a88f60bd3c0bc3c8a0e721dd4985be965dd5d508118e05c",
"view_tag": "13"
}
}
}
],
"extra": [ 1, 75, 28, 136, 84, 84, 67, 95, 51, 101, 78, 56, 188, 155, 146, 23, 171, 151, 148, 108, 137, 178, 200, 131, 210, 156, 56, 105, 126, 51, 97, 61, 134, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}