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: 187aa41eefa48f44de7c085af09dc3f5070dd25adb355d759d3a32ec2ca319e7
Tx prefix hash: f2d0ccce1afb3ee4f59320182cbd30ffbae86aa70c54926ec78789e9c3a485c7
Tx public key: 804eb7ae81dd6815774c5d85fc3cf7810a05a015b042463db469a3120b829b57
| Timestamp: 1779630335 | Timestamp [UTC]: 2026-05-24 13:45:35 | Age [y:d:h:m:s]: 00:015:11:50:22 |
| Block: 867 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7019 | RingCT/type: yes/0 |
| Extra: 01804eb7ae81dd6815774c5d85fc3cf7810a05a015b042463db469a3120b829b57020900000001ba6d17be00 | ||
1 output(s) for total of 35.126303728157 HMNY
| stealth address | amount | amount idx | tag |
| 00: e840dc099fac81890b313d2b0b952888223cf01367087876b60e75ab2870e743 | 35.126303728157 | 999 of 0 | <ef> |
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": 927,
"vin": [ {
"gen": {
"height": 867
}
}
],
"vout": [ {
"amount": 35126303728157,
"target": {
"tagged_key": {
"key": "e840dc099fac81890b313d2b0b952888223cf01367087876b60e75ab2870e743",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 128, 78, 183, 174, 129, 221, 104, 21, 119, 76, 93, 133, 252, 60, 247, 129, 10, 5, 160, 21, 176, 66, 70, 61, 180, 105, 163, 18, 11, 130, 155, 87, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}