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: 8e56aa60e50d7b88cf1da7b51edfa7b189b95e87c88354f9190cc1c681708cf7
Tx prefix hash: 34e025a230ef3f92d8d01bfaaf7a10f7a867803caf2e90140b73e8d46ece5872
Tx public key: 1be3add79d04a1f3a8585ae5d5843c3fb39859cdf9c4bf833b63e106d72974f2
| Timestamp: 1779894402 | Timestamp [UTC]: 2026-05-27 15:06:42 | Age [y:d:h:m:s]: 00:012:10:29:15 |
| Block: 3089 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4797 | RingCT/type: yes/0 |
| Extra: 011be3add79d04a1f3a8585ae5d5843c3fb39859cdf9c4bf833b63e106d72974f202090000000126697be300 | ||
1 output(s) for total of 34.977748811643 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0a5737d9660587efe8ea9dcd229e1b65a25254fa80cc69488e4054886b269408 | 34.977748811643 | 3681 of 0 | <f1> |
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": 3149,
"vin": [ {
"gen": {
"height": 3089
}
}
],
"vout": [ {
"amount": 34977748811643,
"target": {
"tagged_key": {
"key": "0a5737d9660587efe8ea9dcd229e1b65a25254fa80cc69488e4054886b269408",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 27, 227, 173, 215, 157, 4, 161, 243, 168, 88, 90, 229, 213, 132, 60, 63, 179, 152, 89, 205, 249, 196, 191, 131, 59, 99, 225, 6, 215, 41, 116, 242, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}