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: a9195fc5f1b01eae90e093d325de1c08bf71d6d5a89e39bd4c221015c6bd1b5d
Tx prefix hash: 119458c61f1c6e8bcf9cfe247a15ae334fed874237d2ba2dc39368f1802d47d9
Tx public key: e77f9489647c4e5c22bf781f57d4e9314d9299a62b18adf077a341820f952a0a
| Timestamp: 1780033823 | Timestamp [UTC]: 2026-05-29 05:50:23 | Age [y:d:h:m:s]: 00:010:20:50:13 |
| Block: 4222 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3674 | RingCT/type: yes/0 |
| Extra: 01e77f9489647c4e5c22bf781f57d4e9314d9299a62b18adf077a341820f952a0a02090000000326697be300 | ||
1 output(s) for total of 34.905565329901 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4881e89ecceab1239ff1db09ee788426dcb0ceb4910e13682b338906a6d2b68e | 34.905565329901 | 5261 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": 4282,
"vin": [ {
"gen": {
"height": 4222
}
}
],
"vout": [ {
"amount": 34905565329901,
"target": {
"tagged_key": {
"key": "4881e89ecceab1239ff1db09ee788426dcb0ceb4910e13682b338906a6d2b68e",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 231, 127, 148, 137, 100, 124, 78, 92, 34, 191, 120, 31, 87, 212, 233, 49, 77, 146, 153, 166, 43, 24, 173, 240, 119, 163, 65, 130, 15, 149, 42, 10, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}