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: e6b34abecde0db3d5cca5978733aff2bcdea52e5d4dc3e5d7064b33adeb25175
Tx prefix hash: 797036a838cfeea4634b794c2ba284013529b7250fab4bcd84d60886e66467a9
Tx public key: 59e15086888b186fdc9b09ebf29e7f9347ce10f6ed24c1b3e89a40256a13ed25
| Timestamp: 1779938495 | Timestamp [UTC]: 2026-05-28 03:21:35 | Age [y:d:h:m:s]: 00:011:22:14:22 |
| Block: 3463 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4423 | RingCT/type: yes/0 |
| Extra: 0159e15086888b186fdc9b09ebf29e7f9347ce10f6ed24c1b3e89a40256a13ed2502090000000326697be300 | ||
1 output(s) for total of 34.952806364487 HMNY
| stealth address | amount | amount idx | tag |
| 00: 156719368af733ffc8aae4d8a29583ae322728096af041bdf4a74eabb1118f5f | 34.952806364487 | 4180 of 0 | <12> |
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": 3523,
"vin": [ {
"gen": {
"height": 3463
}
}
],
"vout": [ {
"amount": 34952806364487,
"target": {
"tagged_key": {
"key": "156719368af733ffc8aae4d8a29583ae322728096af041bdf4a74eabb1118f5f",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 89, 225, 80, 134, 136, 139, 24, 111, 220, 155, 9, 235, 242, 158, 127, 147, 71, 206, 16, 246, 237, 36, 193, 179, 232, 154, 64, 37, 106, 19, 237, 37, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}