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: 24f3d32774a530dc59c8d9844c240d9046ef77a7cb9f352963b69ca894369c49
Tx prefix hash: 4cad5f8f9f5c154e1eeb9f5403dbb5f3000339bc3bc895826e718218377e1327
Tx public key: e45451d9d16b321ec5cbcc63b2f486cc9176e6fa0d6256a18758e3316eeb8499
| Timestamp: 1779434819 | Timestamp [UTC]: 2026-05-22 07:26:59 | Age [y:d:h:m:s]: 00:017:18:08:58 |
| Block: 104 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7782 | RingCT/type: yes/0 |
| Extra: 01e45451d9d16b321ec5cbcc63b2f486cc9176e6fa0d6256a18758e3316eeb8499020900000001a662ed0300 | ||
1 output(s) for total of 35.177460548294 HMNY
| stealth address | amount | amount idx | tag |
| 00: 352e5c50e9d4480da6aed12b13ae26ded3d50152d6b7973cb79078e99d72b5f0 | 35.177460548294 | 100 of 0 | <70> |
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": 164,
"vin": [ {
"gen": {
"height": 104
}
}
],
"vout": [ {
"amount": 35177460548294,
"target": {
"tagged_key": {
"key": "352e5c50e9d4480da6aed12b13ae26ded3d50152d6b7973cb79078e99d72b5f0",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 228, 84, 81, 217, 209, 107, 50, 30, 197, 203, 204, 99, 178, 244, 134, 204, 145, 118, 230, 250, 13, 98, 86, 161, 135, 88, 227, 49, 110, 235, 132, 153, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}