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: 18d3bd694970221d47ade2a78382b1386a5c321cdd2a9046848dbc08c0b73353
Tx prefix hash: 1f463b457534be141c470a362c21eb1020c0d12e3fdaa01dce9b25b8cdf3102c
Tx public key: 8416561a0feb7a1e501329ffb61a462853dd19dfba746ef6caf49ed228966b68
| Timestamp: 1780691151 | Timestamp [UTC]: 2026-06-05 20:25:51 | Age [y:d:h:m:s]: 00:003:04:20:56 |
| Block: 5712 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2174 | RingCT/type: yes/0 |
| Extra: 018416561a0feb7a1e501329ffb61a462853dd19dfba746ef6caf49ed228966b68020900000002e49593ff00 | ||
1 output(s) for total of 34.803192839801 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf578edfdec4f264767bd527eb64ebbb9bf906a70be53e5babc0d249c412fc1e | 34.803192839801 | 7163 of 0 | <e0> |
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": 5772,
"vin": [ {
"gen": {
"height": 5712
}
}
],
"vout": [ {
"amount": 34803192839801,
"target": {
"tagged_key": {
"key": "cf578edfdec4f264767bd527eb64ebbb9bf906a70be53e5babc0d249c412fc1e",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 132, 22, 86, 26, 15, 235, 122, 30, 80, 19, 41, 255, 182, 26, 70, 40, 83, 221, 25, 223, 186, 116, 110, 246, 202, 244, 158, 210, 40, 150, 107, 104, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}