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: 0eddc4646c6929fd01d695f29a6d7203b61462fd8d80df7ebd923ef4c87bcd6e
Tx prefix hash: 11d888159446f23adc21b0be5cbd239e9fdca95d8613f0751b323b835dc6dc1a
Tx public key: f945f90b00bb9a8f50de646589e80dc1c2375c099fa1279e5b80a803d573dc9b
| Timestamp: 1780323275 | Timestamp [UTC]: 2026-06-01 14:14:35 | Age [y:d:h:m:s]: 00:015:18:14:37 |
| Block: 5096 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3649 | RingCT/type: yes/0 |
| Extra: 01f945f90b00bb9a8f50de646589e80dc1c2375c099fa1279e5b80a803d573dc9b02090000002a26697be300 | ||
1 output(s) for total of 34.844108112863 HMNY
| stealth address | amount | amount idx | tag |
| 00: ca6fd6819bff8bfc36501ee058bdbe67742fe29d11dca3d0cd9b515c75dbcf4e | 34.844108112863 | 6471 of 0 | <00> |
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": 5156,
"vin": [ {
"gen": {
"height": 5096
}
}
],
"vout": [ {
"amount": 34844108112863,
"target": {
"tagged_key": {
"key": "ca6fd6819bff8bfc36501ee058bdbe67742fe29d11dca3d0cd9b515c75dbcf4e",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 249, 69, 249, 11, 0, 187, 154, 143, 80, 222, 100, 101, 137, 232, 13, 193, 194, 55, 92, 9, 159, 161, 39, 158, 91, 128, 168, 3, 213, 115, 220, 155, 2, 9, 0, 0, 0, 42, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}