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: 2a1faf9c32befbebfb95689ef565a048c210095e5d3012217562dbb9c217b970
Tx prefix hash: 68892b6abefaccc85e60bf4f27bd8056ea07e35d2dd29fef3e94f4bbc32dd9d1
Tx public key: fed05ea78a5a2d1d01fff835ddad0a932b8be7924bfa914e6c8beea6e5ef88c6
| Timestamp: 1780689523 | Timestamp [UTC]: 2026-06-05 19:58:43 | Age [y:d:h:m:s]: 00:011:13:16:23 |
| Block: 5602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3143 | RingCT/type: yes/0 |
| Extra: 01fed05ea78a5a2d1d01fff835ddad0a932b8be7924bfa914e6c8beea6e5ef88c6020900000001e49593ff00 | ||
1 output(s) for total of 34.810495613281 HMNY
| stealth address | amount | amount idx | tag |
| 00: 329abdd859908da0891cdb55f27e59f46114ea5feb7f44ce53780c9544ac3066 | 34.810495613281 | 7047 of 0 | <48> |
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": 5662,
"vin": [ {
"gen": {
"height": 5602
}
}
],
"vout": [ {
"amount": 34810495613281,
"target": {
"tagged_key": {
"key": "329abdd859908da0891cdb55f27e59f46114ea5feb7f44ce53780c9544ac3066",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 254, 208, 94, 167, 138, 90, 45, 29, 1, 255, 248, 53, 221, 173, 10, 147, 43, 139, 231, 146, 75, 250, 145, 78, 108, 139, 238, 166, 229, 239, 136, 198, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}