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: 6b19966ddc7a036b965e834013a93e5d7ba5ad44527eefb07fde0cb2958e2dcf
Tx prefix hash: c72e6b3287ad762cfb61effe2b45bc81b8a773bf737f73b074790cf16252d919
Tx public key: ac0a4570feba135c6ce0cf98132d21f9fe9e4b2faf7e2537f8a15a3797011139
| Timestamp: 1779447264 | Timestamp [UTC]: 2026-05-22 10:54:24 | Age [y:d:h:m:s]: 00:017:15:46:12 |
| Block: 281 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7615 | RingCT/type: yes/0 |
| Extra: 01ac0a4570feba135c6ce0cf98132d21f9fe9e4b2faf7e2537f8a15a37970111390209000000014438f87f00 | ||
1 output(s) for total of 35.165586605822 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1521fe5d8624393760135c36c3225684d2732b46329ddd37dae3e39cda398d7d | 35.165586605822 | 277 of 0 | <c5> |
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": 341,
"vin": [ {
"gen": {
"height": 281
}
}
],
"vout": [ {
"amount": 35165586605822,
"target": {
"tagged_key": {
"key": "1521fe5d8624393760135c36c3225684d2732b46329ddd37dae3e39cda398d7d",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 172, 10, 69, 112, 254, 186, 19, 92, 108, 224, 207, 152, 19, 45, 33, 249, 254, 158, 75, 47, 175, 126, 37, 55, 248, 161, 90, 55, 151, 1, 17, 57, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}