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: 5a83b64834aca1237af566f6fbe1adf9b24d091da022986ab802809b043011b6
Tx prefix hash: b2d3fdd7d25a3af250b8d71acc3461962290fb4d9ff0617b942cf5fe6a8e4084
Tx public key: 8356de66e9555cb589b97b99abc4613edf3d9881f18fe0a4f94b5da5b61f3520
| Timestamp: 1780693628 | Timestamp [UTC]: 2026-06-05 21:07:08 | Age [y:d:h:m:s]: 00:003:05:33:28 |
| Block: 5882 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2015 | RingCT/type: yes/0 |
| Extra: 018356de66e9555cb589b97b99abc4613edf3d9881f18fe0a4f94b5da5b61f3520020900000001e49593ff00 | ||
1 output(s) for total of 34.791909748619 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7bd69399a651c879053aee09434e8796dec9aa351816730d26268e6b4fa7e183 | 34.791909748619 | 7341 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": 5942,
"vin": [ {
"gen": {
"height": 5882
}
}
],
"vout": [ {
"amount": 34791909748619,
"target": {
"tagged_key": {
"key": "7bd69399a651c879053aee09434e8796dec9aa351816730d26268e6b4fa7e183",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 131, 86, 222, 102, 233, 85, 92, 181, 137, 185, 123, 153, 171, 196, 97, 62, 223, 61, 152, 129, 241, 143, 224, 164, 249, 75, 93, 165, 182, 31, 53, 32, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}