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: a05fad0fa3fd8a60e4c5e139fbe6348e1a579ddb1b54d01a20640adf64a3a29b
Tx prefix hash: 0dead8342c72469278bdd726da5cdf26482d1e05d4f44d851cf27431f0267c0f
Tx public key: ff399849b70062f7bfe7a8ff4fdbb2633ce168af91b81730193f41c926cb2bb6
| Timestamp: 1780389627 | Timestamp [UTC]: 2026-06-02 08:40:27 | Age [y:d:h:m:s]: 00:006:16:55:30 |
| Block: 5196 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2690 | RingCT/type: yes/0 |
| Extra: 01ff399849b70062f7bfe7a8ff4fdbb2633ce168af91b81730193f41c926cb2bb602090000000126697be300 | ||
1 output(s) for total of 34.837462754100 HMNY
| stealth address | amount | amount idx | tag |
| 00: f38a7efba05b6c9d0b571d00afa275664301206ed1d07266c71d09e9364d234f | 34.837462754100 | 6577 of 0 | <c4> |
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": 5256,
"vin": [ {
"gen": {
"height": 5196
}
}
],
"vout": [ {
"amount": 34837462754100,
"target": {
"tagged_key": {
"key": "f38a7efba05b6c9d0b571d00afa275664301206ed1d07266c71d09e9364d234f",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 255, 57, 152, 73, 183, 0, 98, 247, 191, 231, 168, 255, 79, 219, 178, 99, 60, 225, 104, 175, 145, 184, 23, 48, 25, 63, 65, 201, 38, 203, 43, 182, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}