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: ebb8c3c1e2a8f799f5fd3e3aa8a5514b796ea687732edba5d3fee90938e2d8de
Tx prefix hash: 589bea74d79201bf960afa841d83ad1895f11c53dcec3fed290f4454b1c7d021
Tx public key: c6018378ee7867279ab22239fba8210ee05453c8d8616a1b0f8e7c7745d6e9c2
| Timestamp: 1779713972 | Timestamp [UTC]: 2026-05-25 12:59:32 | Age [y:d:h:m:s]: 00:015:04:09:31 |
| Block: 1609 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7126 | RingCT/type: yes/0 |
| Extra: 01c6018378ee7867279ab22239fba8210ee05453c8d8616a1b0f8e7c7745d6e9c2020900000001ba6d17be00 | ||
1 output(s) for total of 35.076626246482 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ff68080c1aa3fee085f8670f150030a8c86910ae2ec7da20b1e34887045ad6e | 35.076626246482 | 1767 of 0 | <31> |
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": 1669,
"vin": [ {
"gen": {
"height": 1609
}
}
],
"vout": [ {
"amount": 35076626246482,
"target": {
"tagged_key": {
"key": "7ff68080c1aa3fee085f8670f150030a8c86910ae2ec7da20b1e34887045ad6e",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 198, 1, 131, 120, 238, 120, 103, 39, 154, 178, 34, 57, 251, 168, 33, 14, 224, 84, 83, 200, 216, 97, 106, 27, 15, 142, 124, 119, 69, 214, 233, 194, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}