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: 3a7eedf660e4dc285655b8c6e074c2f84955264cbb3927a5bb5ca300f63f2888
Tx prefix hash: d806c423d9dac66d29c3b98c443d46d750180886706ad39eafe659ed01b757d7
Tx public key: 15d3d969b80121bf48c4d8e10620adc43d6e94ef1969ce3ebbc9685d9fb0714f
| Timestamp: 1779648177 | Timestamp [UTC]: 2026-05-24 18:42:57 | Age [y:d:h:m:s]: 00:015:06:53:00 |
| Block: 1464 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6422 | RingCT/type: yes/0 |
| Extra: 0115d3d969b80121bf48c4d8e10620adc43d6e94ef1969ce3ebbc9685d9fb0714f020900000001ba6d17be00 | ||
1 output(s) for total of 35.086328583831 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9318089f56c1041e98336a275b08a789b41df399896b9706b34cd09381a0d5b3 | 35.086328583831 | 1618 of 0 | <ae> |
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": 1524,
"vin": [ {
"gen": {
"height": 1464
}
}
],
"vout": [ {
"amount": 35086328583831,
"target": {
"tagged_key": {
"key": "9318089f56c1041e98336a275b08a789b41df399896b9706b34cd09381a0d5b3",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 21, 211, 217, 105, 184, 1, 33, 191, 72, 196, 216, 225, 6, 32, 173, 196, 61, 110, 148, 239, 25, 105, 206, 62, 187, 201, 104, 93, 159, 176, 113, 79, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}