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: a2ad02f9f0154591dfab975ecd9ca4b378c5f62ce4028500c356a3db9e7a4136
Tx prefix hash: fbab3f02e9102c25701c6c148cb7efcb5822d755fa6ba2f6cb92f58a30b21bdd
Tx public key: d508fc86cfb54b0069de6583babf07033bb694812730b2780f40b58ae2a4ab5c
| Timestamp: 1779795100 | Timestamp [UTC]: 2026-05-26 11:31:40 | Age [y:d:h:m:s]: 00:013:15:18:08 |
| Block: 2259 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5661 | RingCT/type: yes/0 |
| Extra: 01d508fc86cfb54b0069de6583babf07033bb694812730b2780f40b58ae2a4ab5c02090000000126697be300 | ||
1 output(s) for total of 35.033165970294 HMNY
| stealth address | amount | amount idx | tag |
| 00: 661473e9c6364773414c76c0ec90885aa11c5d41428cb6137536ed9fc36c70c8 | 35.033165970294 | 2625 of 0 | <2d> |
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": 2319,
"vin": [ {
"gen": {
"height": 2259
}
}
],
"vout": [ {
"amount": 35033165970294,
"target": {
"tagged_key": {
"key": "661473e9c6364773414c76c0ec90885aa11c5d41428cb6137536ed9fc36c70c8",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 213, 8, 252, 134, 207, 181, 75, 0, 105, 222, 101, 131, 186, 191, 7, 3, 59, 182, 148, 129, 39, 48, 178, 120, 15, 64, 181, 138, 226, 164, 171, 92, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}