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: 12e16adf7f775d06622fd15ae8092e77661ffca2ac723a5c3607821c066f6f9a
Tx prefix hash: 425be3d02381001b21f478bfc4993ea685fc926447ea3977037208bcf54d2246
Tx public key: 48037d7c1eebd2b678f0a0af20999da8bafc09851f03ac5c9f26cb012bb0ce9b
| Timestamp: 1779842414 | Timestamp [UTC]: 2026-05-27 00:40:14 | Age [y:d:h:m:s]: 00:013:02:09:34 |
| Block: 2408 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5512 | RingCT/type: yes/0 |
| Extra: 0148037d7c1eebd2b678f0a0af20999da8bafc09851f03ac5c9f26cb012bb0ce9b02090000000126697be300 | ||
1 output(s) for total of 35.027417126705 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5fb4792f73dcfe8c9e2f2c840d3443dc61e4e7be565cdc4e1426e8cda3b6ef7c | 35.027417126705 | 2826 of 0 | <19> |
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": 2468,
"vin": [ {
"gen": {
"height": 2408
}
}
],
"vout": [ {
"amount": 35027417126705,
"target": {
"tagged_key": {
"key": "5fb4792f73dcfe8c9e2f2c840d3443dc61e4e7be565cdc4e1426e8cda3b6ef7c",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 72, 3, 125, 124, 30, 235, 210, 182, 120, 240, 160, 175, 32, 153, 157, 168, 186, 252, 9, 133, 31, 3, 172, 92, 159, 38, 203, 1, 43, 176, 206, 155, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}