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: dc407a82fe7b96dc1d8cfe8576dae95fc1518a590c64d75b8a034143d4fe50a1
Tx prefix hash: bdc300bcb2ff7f962c1ab89ce33fbc5d6106c90dc8004f9dbd89e2de2c1b84bd
Tx public key: 8589b28dd852dc0501542b60f9e97356e119c01f5588cc0f2c7f851de0620425
| Timestamp: 1779844941 | Timestamp [UTC]: 2026-05-27 01:22:21 | Age [y:d:h:m:s]: 00:012:23:24:26 |
| Block: 2439 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5447 | RingCT/type: yes/0 |
| Extra: 018589b28dd852dc0501542b60f9e97356e119c01f5588cc0f2c7f851de062042502090000000126697be300 | ||
1 output(s) for total of 35.021140340261 HMNY
| stealth address | amount | amount idx | tag |
| 00: 77f204934d8385c9bf4304bf2d72d8d6d28e5781e0a0cc77d4c8c1d0486e458e | 35.021140340261 | 2867 of 0 | <9f> |
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": 2499,
"vin": [ {
"gen": {
"height": 2439
}
}
],
"vout": [ {
"amount": 35021140340261,
"target": {
"tagged_key": {
"key": "77f204934d8385c9bf4304bf2d72d8d6d28e5781e0a0cc77d4c8c1d0486e458e",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 133, 137, 178, 141, 216, 82, 220, 5, 1, 84, 43, 96, 249, 233, 115, 86, 225, 25, 192, 31, 85, 136, 204, 15, 44, 127, 133, 29, 224, 98, 4, 37, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}