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: bf15615c2fbb20bca3365c1d5f4beed1ed9a4b264e7d008f7a90c3ea9cb17986
Tx prefix hash: 2f34e52732e21cc43f211da662afb16ede51eaebd4bfc007a914d296906b03ad
Tx public key: 07c87e3c2a28befc89536315e1175d0fd71e5d02000669cc27ba1cdf0180ad72
| Timestamp: 1779480618 | Timestamp [UTC]: 2026-05-22 20:10:18 | Age [y:d:h:m:s]: 00:017:05:25:39 |
| Block: 647 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7239 | RingCT/type: yes/0 |
| Extra: 0107c87e3c2a28befc89536315e1175d0fd71e5d02000669cc27ba1cdf0180ad7202090000000293369e7d00 | ||
1 output(s) for total of 35.141046418766 HMNY
| stealth address | amount | amount idx | tag |
| 00: 023784b7c890e6aea7dcb566b39aa483c4d3e88d050ecae2f8434f603be77a0f | 35.141046418766 | 690 of 0 | <77> |
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": 707,
"vin": [ {
"gen": {
"height": 647
}
}
],
"vout": [ {
"amount": 35141046418766,
"target": {
"tagged_key": {
"key": "023784b7c890e6aea7dcb566b39aa483c4d3e88d050ecae2f8434f603be77a0f",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 7, 200, 126, 60, 42, 40, 190, 252, 137, 83, 99, 21, 225, 23, 93, 15, 215, 30, 93, 2, 0, 6, 105, 204, 39, 186, 28, 223, 1, 128, 173, 114, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}