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: a53309e52da63d4322c89755346f9f081ef0d3088cd0f4ef039e17588360c300
Tx prefix hash: d5e6369e5aa2f9e7e85c3409f24209318e6fcf3321fc2a92e38a64960d7e3dd2
Tx public key: e6d4e7576aa5a4a24b6a7a2e6bd542401facac6633549f4b796dd99d46f43ec0
| Timestamp: 1780064145 | Timestamp [UTC]: 2026-05-29 14:15:45 | Age [y:d:h:m:s]: 00:010:12:34:03 |
| Block: 4558 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3351 | RingCT/type: yes/0 |
| Extra: 01e6d4e7576aa5a4a24b6a7a2e6bd542401facac6633549f4b796dd99d46f43ec002090000000126697be300 | ||
1 output(s) for total of 34.879881904283 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9132ac18a8384f5898e92feef29c4012ad0cb453d1e943c2bf3337f46c62853c | 34.879881904283 | 5722 of 0 | <50> |
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": 4618,
"vin": [ {
"gen": {
"height": 4558
}
}
],
"vout": [ {
"amount": 34879881904283,
"target": {
"tagged_key": {
"key": "9132ac18a8384f5898e92feef29c4012ad0cb453d1e943c2bf3337f46c62853c",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 230, 212, 231, 87, 106, 165, 164, 162, 75, 106, 122, 46, 107, 213, 66, 64, 31, 172, 172, 102, 51, 84, 159, 75, 121, 109, 217, 157, 70, 244, 62, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}