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: a7da68df5d96fd590bc4a14c012c66f2f48e81ea066076053d92dd2444d09439
Tx prefix hash: a61faccbaafac46827cfa694f2fb9bd46ce7b003e35926a7f31b41e8034ff17c
Tx public key: 4656932a0049521c7a3dde57f85ea35d9e096038e354a9db8eb1b549414a8bd8
| Timestamp: 1779947912 | Timestamp [UTC]: 2026-05-28 05:58:32 | Age [y:d:h:m:s]: 00:011:22:34:30 |
| Block: 3580 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4447 | RingCT/type: yes/0 |
| Extra: 014656932a0049521c7a3dde57f85ea35d9e096038e354a9db8eb1b549414a8bd802090000000126697be300 | ||
1 output(s) for total of 34.948417566385 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24f5b7558f997c29be57b7602556c7b6c3e546db4996fc1100de45f395e085da | 34.948417566385 | 4321 of 0 | <f9> |
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": 3640,
"vin": [ {
"gen": {
"height": 3580
}
}
],
"vout": [ {
"amount": 34948417566385,
"target": {
"tagged_key": {
"key": "24f5b7558f997c29be57b7602556c7b6c3e546db4996fc1100de45f395e085da",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 70, 86, 147, 42, 0, 73, 82, 28, 122, 61, 222, 87, 248, 94, 163, 93, 158, 9, 96, 56, 227, 84, 169, 219, 142, 177, 181, 73, 65, 74, 139, 216, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}