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: 493a5cd34467a70c99e55710fdc26ca10fdc8154175da7c06d2707015432fa36
Tx prefix hash: 4807c5d472f640130f841a0fba8348ecd4b884ef8f1f1a0084d3d898de325d5c
Tx public key: c8c2ad48cfa2d3e1b1b9b4f7edba0e3779c030830afdc26f4657f8ee14fc7149
| Timestamp: 1780819613 | Timestamp [UTC]: 2026-06-07 08:06:53 | Age [y:d:h:m:s]: 00:010:00:29:21 |
| Block: 7141 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1604 | RingCT/type: yes/0 |
| Extra: 01c8c2ad48cfa2d3e1b1b9b4f7edba0e3779c030830afdc26f4657f8ee14fc7149020900000001e49593ff00 | ||
1 output(s) for total of 34.708462282925 HMNY
| stealth address | amount | amount idx | tag |
| 00: 87db5ca18586c7fe0792e52f553e6f11603f0f2bfac1c2aaf71b152b67bda346 | 34.708462282925 | 8799 of 0 | <d7> |
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": 7201,
"vin": [ {
"gen": {
"height": 7141
}
}
],
"vout": [ {
"amount": 34708462282925,
"target": {
"tagged_key": {
"key": "87db5ca18586c7fe0792e52f553e6f11603f0f2bfac1c2aaf71b152b67bda346",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 200, 194, 173, 72, 207, 162, 211, 225, 177, 185, 180, 247, 237, 186, 14, 55, 121, 192, 48, 131, 10, 253, 194, 111, 70, 87, 248, 238, 20, 252, 113, 73, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}