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: b1fb284307398e809f3016be892800c434a38f6a3255d2ffd79888997a82d215
Tx prefix hash: a866e3f435d9dca4fba449b2ef30ad6101e24e9150020a10e938cbeaa22e7e2a
Tx public key: aed9a03b4df869eccf6f821a6052aed779f73ca5879b0e949c1c8665411459ec
| Timestamp: 1779932095 | Timestamp [UTC]: 2026-05-28 01:34:55 | Age [y:d:h:m:s]: 00:012:00:01:02 |
| Block: 3406 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4480 | RingCT/type: yes/0 |
| Extra: 01aed9a03b4df869eccf6f821a6052aed779f73ca5879b0e949c1c8665411459ec02090000000126697be300 | ||
1 output(s) for total of 34.956606604370 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9743b4114772f3c9b75de60eeb4a6c4589ef7a98bdcbdb7de552912ef8cb884f | 34.956606604370 | 4121 of 0 | <6d> |
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": 3466,
"vin": [ {
"gen": {
"height": 3406
}
}
],
"vout": [ {
"amount": 34956606604370,
"target": {
"tagged_key": {
"key": "9743b4114772f3c9b75de60eeb4a6c4589ef7a98bdcbdb7de552912ef8cb884f",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 174, 217, 160, 59, 77, 248, 105, 236, 207, 111, 130, 26, 96, 82, 174, 215, 121, 247, 60, 165, 135, 155, 14, 148, 156, 28, 134, 101, 65, 20, 89, 236, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}