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: 509bfb01bc6767af24e2b5c3a75ffdfb453d0dad5cd992531f3235b7425ddbc8
Tx prefix hash: bb8e2075dcef1ec571f44015c9b1efd0078def9caf468d5b21e9b3d75c239c5b
Tx public key: 746fd06ddb2333e335bd34e6096db0af306eaf85ba8bca186eb4b6084b4a8889
| Timestamp: 1779840112 | Timestamp [UTC]: 2026-05-27 00:01:52 | Age [y:d:h:m:s]: 00:013:02:38:44 |
| Block: 2378 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5517 | RingCT/type: yes/0 |
| Extra: 01746fd06ddb2333e335bd34e6096db0af306eaf85ba8bca186eb4b6084b4a888902090000000126697be300 | ||
1 output(s) for total of 35.025215230169 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7560b7c4e51ad3a3f997b9bc67a15aa2617c95acf8d4cdad151ce76b12b0ba35 | 35.025215230169 | 2790 of 0 | <6d> |
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": 2438,
"vin": [ {
"gen": {
"height": 2378
}
}
],
"vout": [ {
"amount": 35025215230169,
"target": {
"tagged_key": {
"key": "7560b7c4e51ad3a3f997b9bc67a15aa2617c95acf8d4cdad151ce76b12b0ba35",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 116, 111, 208, 109, 219, 35, 51, 227, 53, 189, 52, 230, 9, 109, 176, 175, 48, 110, 175, 133, 186, 139, 202, 24, 110, 180, 182, 8, 75, 74, 136, 137, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}