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: 8cb2f5f0b6de5db6bd993a7c42d22a6cd47a9b5b61d5f614cfdd36c07b7441a5
Tx prefix hash: d9dac34cb31bb05b30d8e025dcae7bbd4bde085de34ed118950d953bfa6a6200
Tx public key: 96794baa1e24a0db37c6f30a0c16e264ffae24989dac5470faa34c103fc051bd
| Timestamp: 1779864508 | Timestamp [UTC]: 2026-05-27 06:48:28 | Age [y:d:h:m:s]: 00:019:01:31:07 |
| Block: 2724 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6021 | RingCT/type: yes/0 |
| Extra: 0196794baa1e24a0db37c6f30a0c16e264ffae24989dac5470faa34c103fc051bd02090000000126697be300 | ||
1 output(s) for total of 35.008713001079 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae90605f0bb2c70d52a2c0bb4a61d5eefd5e3debe4702f1a061af2b4f7173d4a | 35.008713001079 | 3216 of 0 | <dd> |
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": 2784,
"vin": [ {
"gen": {
"height": 2724
}
}
],
"vout": [ {
"amount": 35008713001079,
"target": {
"tagged_key": {
"key": "ae90605f0bb2c70d52a2c0bb4a61d5eefd5e3debe4702f1a061af2b4f7173d4a",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 150, 121, 75, 170, 30, 36, 160, 219, 55, 198, 243, 10, 12, 22, 226, 100, 255, 174, 36, 152, 157, 172, 84, 112, 250, 163, 76, 16, 63, 192, 81, 189, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}