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: 754b3fc8fc32b24f535a016a8ab373160648c542fc5dba50e7a4cfb20d8cdfea
Tx prefix hash: 81e89c2c3c101f92f2e8029dad6edf9dc0572bc2b0379550c3c58c4702c97a4d
Tx public key: 70c124744b5d1c6e0b9690f89cf782358cb6c07d745dd9d3b17061518b918da3
| Timestamp: 1780031387 | Timestamp [UTC]: 2026-05-29 05:09:47 | Age [y:d:h:m:s]: 00:010:20:26:10 |
| Block: 4203 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3683 | RingCT/type: yes/0 |
| Extra: 0170c124744b5d1c6e0b9690f89cf782358cb6c07d745dd9d3b17061518b918da302090000000326697be300 | ||
1 output(s) for total of 34.903507398173 HMNY
| stealth address | amount | amount idx | tag |
| 00: ecf38f3e8f3453197074f0cea09bd454a9c8d9a84e17424b5a47505ea73ac242 | 34.903507398173 | 5238 of 0 | <4a> |
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": 4263,
"vin": [ {
"gen": {
"height": 4203
}
}
],
"vout": [ {
"amount": 34903507398173,
"target": {
"tagged_key": {
"key": "ecf38f3e8f3453197074f0cea09bd454a9c8d9a84e17424b5a47505ea73ac242",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 112, 193, 36, 116, 75, 93, 28, 110, 11, 150, 144, 248, 156, 247, 130, 53, 140, 182, 192, 125, 116, 93, 217, 211, 177, 112, 97, 81, 139, 145, 141, 163, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}