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: e14fdbdf6210cbf77528cd28cf68a6b9938834d2fc86091f3e399112ad61476d
Tx prefix hash: 5e7eeda67778c3ff2234d54b2f5c2e85a6946a01b64f470e44f02465f63b6c2b
Tx public key: c3aebdac56ab2d1415f9c21e4a5aa80890fbc06cc30a2c615386cea3c30d8643
| Timestamp: 1779454687 | Timestamp [UTC]: 2026-05-22 12:58:07 | Age [y:d:h:m:s]: 00:021:22:04:09 |
| Block: 371 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8374 | RingCT/type: yes/0 |
| Extra: 01c3aebdac56ab2d1415f9c21e4a5aa80890fbc06cc30a2c615386cea3c30d864302090000000193369e7d00 | ||
1 output(s) for total of 35.159550545141 HMNY
| stealth address | amount | amount idx | tag |
| 00: 55c71ae422a97c190065bdeb77e9ac4001b50a2ff0c4bd09716e342e5d73c5d9 | 35.159550545141 | 367 of 0 | <7f> |
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": 431,
"vin": [ {
"gen": {
"height": 371
}
}
],
"vout": [ {
"amount": 35159550545141,
"target": {
"tagged_key": {
"key": "55c71ae422a97c190065bdeb77e9ac4001b50a2ff0c4bd09716e342e5d73c5d9",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 195, 174, 189, 172, 86, 171, 45, 20, 21, 249, 194, 30, 74, 90, 168, 8, 144, 251, 192, 108, 195, 10, 44, 97, 83, 134, 206, 163, 195, 13, 134, 67, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}