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: 3338fbcea79d08a1ab31c29e3eed48bf3bc2875b5d414e427d8deecab2b86b2d
Tx prefix hash: f538f56ae6b7103ece85d8f3630fb5674a66570a41b18c31a71f8b9a98159a4b
Tx public key: 36e0bc7dca5086052fd48814193a0d5f705eef752cb4e66919affffd27ee6a6a
| Timestamp: 1779631296 | Timestamp [UTC]: 2026-05-24 14:01:36 | Age [y:d:h:m:s]: 00:015:13:37:14 |
| Block: 904 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7037 | RingCT/type: yes/0 |
| Extra: 0136e0bc7dca5086052fd48814193a0d5f705eef752cb4e66919affffd27ee6a6a020900000001ba6d17be00 | ||
1 output(s) for total of 35.123824883289 HMNY
| stealth address | amount | amount idx | tag |
| 00: f289c95788f4d9689243b55713b79aa76c0c2ca93d29ca1a1f9ef36349ac4a21 | 35.123824883289 | 1038 of 0 | <82> |
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": 964,
"vin": [ {
"gen": {
"height": 904
}
}
],
"vout": [ {
"amount": 35123824883289,
"target": {
"tagged_key": {
"key": "f289c95788f4d9689243b55713b79aa76c0c2ca93d29ca1a1f9ef36349ac4a21",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 54, 224, 188, 125, 202, 80, 134, 5, 47, 212, 136, 20, 25, 58, 13, 95, 112, 94, 239, 117, 44, 180, 230, 105, 25, 175, 255, 253, 39, 238, 106, 106, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}