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: 42b2a0401163cbce0392d30255f5847976f4bcbf6db0bf6569856b670033744b
Tx prefix hash: 659ee9aed07a44c5d759ab665bff30ab370f7c7775368731f36f97d3a2119f80
Tx public key: e09756ff7a2a87909e612a63c70da197bb08ca2479cc712383c5e512e93f51f4
| Timestamp: 1780982238 | Timestamp [UTC]: 2026-06-09 05:17:18 | Age [y:d:h:m:s]: 00:000:07:20:27 |
| Block: 8059 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 513 | RingCT/type: yes/0 |
| Extra: 01e09756ff7a2a87909e612a63c70da197bb08ca2479cc712383c5e512e93f51f4020900000002e49593ff00 | ||
1 output(s) for total of 34.647742754081 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8561d53d11fb2ea3c322de1c6589f42955da4ba1cb6d42ed338b97a8f0cb429a | 34.647742754081 | 9987 of 0 | <f6> |
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": 8119,
"vin": [ {
"gen": {
"height": 8059
}
}
],
"vout": [ {
"amount": 34647742754081,
"target": {
"tagged_key": {
"key": "8561d53d11fb2ea3c322de1c6589f42955da4ba1cb6d42ed338b97a8f0cb429a",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 224, 151, 86, 255, 122, 42, 135, 144, 158, 97, 42, 99, 199, 13, 161, 151, 187, 8, 202, 36, 121, 204, 113, 35, 131, 197, 229, 18, 233, 63, 81, 244, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}