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: 3fe52fc5ec6888a23525140b7fda37635375fd7128916e202101dd5104c53c28
Tx prefix hash: f0a5506450b655a888fd958a3d0da0faa6c44b8b9765bdb709621f8d441e799a
Tx public key: 880015717ccd5e80eb2e13f5db29cc4829259f3ded4a0d61988d5f30da70abbe
| Timestamp: 1780033845 | Timestamp [UTC]: 2026-05-29 05:50:45 | Age [y:d:h:m:s]: 00:010:18:56:02 |
| Block: 4223 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3663 | RingCT/type: yes/0 |
| Extra: 01880015717ccd5e80eb2e13f5db29cc4829259f3ded4a0d61988d5f30da70abbe02090000000326697be300 | ||
1 output(s) for total of 34.902175959156 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2bf8aa8e8e061743e228f491f3a9b824889e79944878a17c49b8c51c7128253 | 34.902175959156 | 5265 of 0 | <1f> |
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": 4283,
"vin": [ {
"gen": {
"height": 4223
}
}
],
"vout": [ {
"amount": 34902175959156,
"target": {
"tagged_key": {
"key": "d2bf8aa8e8e061743e228f491f3a9b824889e79944878a17c49b8c51c7128253",
"view_tag": "1f"
}
}
}
],
"extra": [ 1, 136, 0, 21, 113, 124, 205, 94, 128, 235, 46, 19, 245, 219, 41, 204, 72, 41, 37, 159, 61, 237, 74, 13, 97, 152, 141, 95, 48, 218, 112, 171, 190, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}