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: c82c7d054995c5ae57d293c0ba4c1605afcad82fc50a2df80e2158b5893de0d3
Tx prefix hash: 16c29ab5d53449849a0cdc70810594b8b335a1529980f2b7243056e67a629a60
Tx public key: 185e960e9b9be1076bd2f920ba5c0fe3c743bd11e48426d08b4ce2a9d05ae11f
| Timestamp: 1779724717 | Timestamp [UTC]: 2026-05-25 15:58:37 | Age [y:d:h:m:s]: 00:014:09:37:20 |
| Block: 1832 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6054 | RingCT/type: yes/0 |
| Extra: 01185e960e9b9be1076bd2f920ba5c0fe3c743bd11e48426d08b4ce2a9d05ae11f020900000001ba6d17be00 | ||
1 output(s) for total of 35.061709956529 HMNY
| stealth address | amount | amount idx | tag |
| 00: 03e40abe197b08b8cda415c7c0d823c4ea27a850665fc0b4cbe40b3a69cae95e | 35.061709956529 | 2026 of 0 | <35> |
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": 1892,
"vin": [ {
"gen": {
"height": 1832
}
}
],
"vout": [ {
"amount": 35061709956529,
"target": {
"tagged_key": {
"key": "03e40abe197b08b8cda415c7c0d823c4ea27a850665fc0b4cbe40b3a69cae95e",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 24, 94, 150, 14, 155, 155, 225, 7, 107, 210, 249, 32, 186, 92, 15, 227, 199, 67, 189, 17, 228, 132, 38, 208, 139, 76, 226, 169, 208, 90, 225, 31, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}