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: 9155d64cc9d516197ca0b87f4cae3fa8780ea5c60a00ddb8c1be12d272dd860f
Tx prefix hash: bfaefa87cf304b12b428c52e2509f0504e5768ac30734d12447a17b1335ce513
Tx public key: b745f5898dc185002ad4eb8187c9ef91045ca3770744972710b6ba4f47a0fcb9
| Timestamp: 1779444734 | Timestamp [UTC]: 2026-05-22 10:12:14 | Age [y:d:h:m:s]: 00:017:18:20:48 |
| Block: 260 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7756 | RingCT/type: yes/0 |
| Extra: 01b745f5898dc185002ad4eb8187c9ef91045ca3770744972710b6ba4f47a0fcb90209000000014438f87f00 | ||
1 output(s) for total of 35.166995169078 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8d87ebc07a034ec5ef7e8061a7bdffb170c940b642c950ac82099a3a59349a85 | 35.166995169078 | 256 of 0 | <f3> |
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": 320,
"vin": [ {
"gen": {
"height": 260
}
}
],
"vout": [ {
"amount": 35166995169078,
"target": {
"tagged_key": {
"key": "8d87ebc07a034ec5ef7e8061a7bdffb170c940b642c950ac82099a3a59349a85",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 183, 69, 245, 137, 141, 193, 133, 0, 42, 212, 235, 129, 135, 201, 239, 145, 4, 92, 163, 119, 7, 68, 151, 39, 16, 182, 186, 79, 71, 160, 252, 185, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}