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: d6c44ce037fb2a33908afd5e9bd647e4328c2ffbd291ae9519669fadad2e0617
Tx prefix hash: 96cfc2ca499c6c24b34d730279a29b1ae41f946860b17cf955235c6e73de2a1d
Tx public key: d1456a5752c7ef2a18d30147140b6d3fe2571877869642174b89e369b6ca5dc8
| Timestamp: 1779456084 | Timestamp [UTC]: 2026-05-22 13:21:24 | Age [y:d:h:m:s]: 00:017:14:17:26 |
| Block: 385 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7559 | RingCT/type: yes/0 |
| Extra: 01d1456a5752c7ef2a18d30147140b6d3fe2571877869642174b89e369b6ca5dc802090000000793369e7d00 | ||
1 output(s) for total of 35.158611695492 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe201ab4ba9270197bd64aca33304f85eefcab4b0f1ef449851c028c0a4c188a | 35.158611695492 | 383 of 0 | <ff> |
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": 445,
"vin": [ {
"gen": {
"height": 385
}
}
],
"vout": [ {
"amount": 35158611695492,
"target": {
"tagged_key": {
"key": "fe201ab4ba9270197bd64aca33304f85eefcab4b0f1ef449851c028c0a4c188a",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 209, 69, 106, 87, 82, 199, 239, 42, 24, 211, 1, 71, 20, 11, 109, 63, 226, 87, 24, 119, 134, 150, 66, 23, 75, 137, 227, 105, 182, 202, 93, 200, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}