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: b7893d6e7f9aec18449fdaf9fd2f5105511a8e70566f85b2779e9735436d3af4
Tx prefix hash: 753c1d2fafa43134ddc053f8be6ee5d013152af822f33de2e9cbbba18d47a096
Tx public key: 6bbc52e47a8da9d3d1f2b7d904d432118ff9713ee9c433ade24e84e072b6d2ff
| Timestamp: 1780864999 | Timestamp [UTC]: 2026-06-07 20:43:19 | Age [y:d:h:m:s]: 00:001:06:06:29 |
| Block: 7654 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 245 | RingCT/type: yes/0 |
| Extra: 016bbc52e47a8da9d3d1f2b7d904d432118ff9713ee9c433ade24e84e072b6d2ff020900000004e49593ff00 | ||
1 output(s) for total of 34.674517676312 HMNY
| stealth address | amount | amount idx | tag |
| 00: 96b32bce2a2064ef55ffe9735f22d5b921818ec76c1ccc3e18ad8373f6465625 | 34.674517676312 | 9464 of 0 | <81> |
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": 7714,
"vin": [ {
"gen": {
"height": 7654
}
}
],
"vout": [ {
"amount": 34674517676312,
"target": {
"tagged_key": {
"key": "96b32bce2a2064ef55ffe9735f22d5b921818ec76c1ccc3e18ad8373f6465625",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 107, 188, 82, 228, 122, 141, 169, 211, 209, 242, 183, 217, 4, 212, 50, 17, 143, 249, 113, 62, 233, 196, 51, 173, 226, 78, 132, 224, 114, 182, 210, 255, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}