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: 3b3c0d3537aae2fb81911efb7ad74b92a1f73db3376020cdab80fff5a079fdd5
Tx prefix hash: 36b469c02140dec3d484afd27b2e32d488e803b36edc07d49c602e12b33ef511
Tx public key: 12b352ae7e9610775418dea400d3868327c6056b62ed4ff91e76d0e84c0bddaf
| Timestamp: 1779765642 | Timestamp [UTC]: 2026-05-26 03:20:42 | Age [y:d:h:m:s]: 00:014:00:18:08 |
| Block: 1966 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5978 | RingCT/type: yes/0 |
| Extra: 0112b352ae7e9610775418dea400d3868327c6056b62ed4ff91e76d0e84c0bddaf02090000000226697be300 | ||
1 output(s) for total of 35.058553055856 HMNY
| stealth address | amount | amount idx | tag |
| 00: a54f1402eea389dddd34d338f86087544760f1987bb1c4168b463d8b82dd3c16 | 35.058553055856 | 2232 of 0 | <a7> |
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": 2026,
"vin": [ {
"gen": {
"height": 1966
}
}
],
"vout": [ {
"amount": 35058553055856,
"target": {
"tagged_key": {
"key": "a54f1402eea389dddd34d338f86087544760f1987bb1c4168b463d8b82dd3c16",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 18, 179, 82, 174, 126, 150, 16, 119, 84, 24, 222, 164, 0, 211, 134, 131, 39, 198, 5, 107, 98, 237, 79, 249, 30, 118, 208, 232, 76, 11, 221, 175, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}