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: e85ffb7a93d16be718854a796428f3b9dd074218ec8bb03ee367a4a775eb2e30
Tx prefix hash: 92b2de9be08f67cb9d7c0c27e9476461e3582aecbb6c712820c36344531e9368
Tx public key: 51340de4d4ca66f566a4b331297e29c897f4425a09b63435c108416b1d9899b0
| Timestamp: 1780890988 | Timestamp [UTC]: 2026-06-08 03:56:28 | Age [y:d:h:m:s]: 00:000:20:50:19 |
| Block: 7723 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 163 | RingCT/type: yes/0 |
| Extra: 0151340de4d4ca66f566a4b331297e29c897f4425a09b63435c108416b1d9899b00209000000024a728a4c00 | ||
1 output(s) for total of 34.669954561058 HMNY
| stealth address | amount | amount idx | tag |
| 00: 485e6c1eea71afef7adf2691421a4eeeadcd560503d5032dc2388d395eee5516 | 34.669954561058 | 9559 of 0 | <c0> |
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": 7783,
"vin": [ {
"gen": {
"height": 7723
}
}
],
"vout": [ {
"amount": 34669954561058,
"target": {
"tagged_key": {
"key": "485e6c1eea71afef7adf2691421a4eeeadcd560503d5032dc2388d395eee5516",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 81, 52, 13, 228, 212, 202, 102, 245, 102, 164, 179, 49, 41, 126, 41, 200, 151, 244, 66, 90, 9, 182, 52, 53, 193, 8, 65, 107, 29, 152, 153, 176, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}