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: 98b85bc21af0c4fe075e5f77d049d9c6dc50840fd24c7eabd547cb845a50b5af
Tx prefix hash: 8f18ec0c3e6f1c1c5a8b9c7f8daea1103a54ea6beb4246c307d9616988335f5e
Tx public key: 32aa07fcfbb460828b466c8f58e1deec31f7d61d11ecb6da930555a740fe9cf2
| Timestamp: 1781016827 | Timestamp [UTC]: 2026-06-09 14:53:47 | Age [y:d:h:m:s]: 00:006:01:49:27 |
| Block: 8642 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 103 | RingCT/type: yes/0 |
| Extra: 0132aa07fcfbb460828b466c8f58e1deec31f7d61d11ecb6da930555a740fe9cf2020900000005e49593ff00 | ||
1 output(s) for total of 34.609236386221 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ce02f9dedfb6f5a7656c44e5af6be69517919230da9957e52760ae1eb11b0be | 34.609236386221 | 10684 of 0 | <72> |
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": 8702,
"vin": [ {
"gen": {
"height": 8642
}
}
],
"vout": [ {
"amount": 34609236386221,
"target": {
"tagged_key": {
"key": "4ce02f9dedfb6f5a7656c44e5af6be69517919230da9957e52760ae1eb11b0be",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 50, 170, 7, 252, 251, 180, 96, 130, 139, 70, 108, 143, 88, 225, 222, 236, 49, 247, 214, 29, 17, 236, 182, 218, 147, 5, 85, 167, 64, 254, 156, 242, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}