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: e3055f157d6b42425fc35c5efeea30592c7a264e6ee4d8f9c562c9deec39efa2
Tx prefix hash: e61d8221af860f43d11aeab84200be003ffc0e32715e3c2add19988d13c4dc6d
Tx public key: eb74c084464fca5a740c4405c584a2a5ad6ea797bd65c6778e6e53f212ac4b6c
| Timestamp: 1780046834 | Timestamp [UTC]: 2026-05-29 09:27:14 | Age [y:d:h:m:s]: 00:010:19:05:48 |
| Block: 4351 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3675 | RingCT/type: yes/0 |
| Extra: 01eb74c084464fca5a740c4405c584a2a5ad6ea797bd65c6778e6e53f212ac4b6c02090000000326697be300 | ||
1 output(s) for total of 34.893655952061 HMNY
| stealth address | amount | amount idx | tag |
| 00: bdada5c744cc3fa0c925475252b9e27a607d431f87256bdedfa0d454ce63fdcd | 34.893655952061 | 5439 of 0 | <97> |
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": 4411,
"vin": [ {
"gen": {
"height": 4351
}
}
],
"vout": [ {
"amount": 34893655952061,
"target": {
"tagged_key": {
"key": "bdada5c744cc3fa0c925475252b9e27a607d431f87256bdedfa0d454ce63fdcd",
"view_tag": "97"
}
}
}
],
"extra": [ 1, 235, 116, 192, 132, 70, 79, 202, 90, 116, 12, 68, 5, 197, 132, 162, 165, 173, 110, 167, 151, 189, 101, 198, 119, 142, 110, 83, 242, 18, 172, 75, 108, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}