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: 78bd076c8d17d168c4f85060ae8eaec5e9b5a1c15039d51186d8707d1633d6b6
Tx prefix hash: 613117b695bebc0121bd833af88cf06eb6595cef0bcecaea28d80cc553cbb5d8
Tx public key: b5b77e666759abe0c04bd70b47946fd4695a6581d88bc938b8591264a14b0aa9
| Timestamp: 1780818337 | Timestamp [UTC]: 2026-06-07 07:45:37 | Age [y:d:h:m:s]: 00:001:17:50:20 |
| Block: 7108 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 778 | RingCT/type: yes/0 |
| Extra: 01b5b77e666759abe0c04bd70b47946fd4695a6581d88bc938b8591264a14b0aa9020900000001e49593ff00 | ||
1 output(s) for total of 34.710646991320 HMNY
| stealth address | amount | amount idx | tag |
| 00: 378ecf5e5764400d6086c44497b0adf6638e723b54dce43f81179fa6203fc6bf | 34.710646991320 | 8762 of 0 | <60> |
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": 7168,
"vin": [ {
"gen": {
"height": 7108
}
}
],
"vout": [ {
"amount": 34710646991320,
"target": {
"tagged_key": {
"key": "378ecf5e5764400d6086c44497b0adf6638e723b54dce43f81179fa6203fc6bf",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 181, 183, 126, 102, 103, 89, 171, 224, 192, 75, 215, 11, 71, 148, 111, 212, 105, 90, 101, 129, 216, 139, 201, 56, 184, 89, 18, 100, 161, 75, 10, 169, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}