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: 122684bc3d0a9a022bdfb1cc5c56732a666da58f1c65bded69291428a9ee3f02
Tx prefix hash: 6b85104e79a99169e5b73816aabaeb47fdf6051fdd1f32eb666ba81029366649
Tx public key: feb6c89a21c58fc65e776ae5e0c63be62081c106d066f86470a2ab4cf8640c3a
| Timestamp: 1780064039 | Timestamp [UTC]: 2026-05-29 14:13:59 | Age [y:d:h:m:s]: 00:010:10:32:48 |
| Block: 4557 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3329 | RingCT/type: yes/0 |
| Extra: 01feb6c89a21c58fc65e776ae5e0c63be62081c106d066f86470a2ab4cf8640c3a02090000000326697be300 | ||
1 output(s) for total of 34.879948432505 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7e74cda91dacadddd584a9b5af098292950fe6ee302b9262fd57ae1b280fe80 | 34.879948432505 | 5721 of 0 | <fa> |
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": 4617,
"vin": [ {
"gen": {
"height": 4557
}
}
],
"vout": [ {
"amount": 34879948432505,
"target": {
"tagged_key": {
"key": "e7e74cda91dacadddd584a9b5af098292950fe6ee302b9262fd57ae1b280fe80",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 254, 182, 200, 154, 33, 197, 143, 198, 94, 119, 106, 229, 224, 198, 59, 230, 32, 129, 193, 6, 208, 102, 248, 100, 112, 162, 171, 76, 248, 100, 12, 58, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}