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: 9f6ffe0ab9f17a3869df1710221fd614a049fb14af62516a0eed8f59ac8f5112
Tx prefix hash: 8499616754c49f8dac089b16ea035307394e83c41200d4c4e3cda7ccdb066be7
Tx public key: 4b6eb362476615a1ef26384c65fe4f3cb82a6c13a8d5c27b7a14a24a88c1f2e7
| Timestamp: 1779960722 | Timestamp [UTC]: 2026-05-28 09:32:02 | Age [y:d:h:m:s]: 00:011:16:03:55 |
| Block: 3756 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4130 | RingCT/type: yes/0 |
| Extra: 014b6eb362476615a1ef26384c65fe4f3cb82a6c13a8d5c27b7a14a24a88c1f2e702090000000326697be300 | ||
1 output(s) for total of 34.933278317109 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0dc1cfed35b8b32eda852ba104ddad4ebd6e3008bc6f1cd965d5ee90632da52a | 34.933278317109 | 4554 of 0 | <c1> |
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": 3816,
"vin": [ {
"gen": {
"height": 3756
}
}
],
"vout": [ {
"amount": 34933278317109,
"target": {
"tagged_key": {
"key": "0dc1cfed35b8b32eda852ba104ddad4ebd6e3008bc6f1cd965d5ee90632da52a",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 75, 110, 179, 98, 71, 102, 21, 161, 239, 38, 56, 76, 101, 254, 79, 60, 184, 42, 108, 19, 168, 213, 194, 123, 122, 20, 162, 74, 136, 193, 242, 231, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}