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: 5e4465c2b2ccc953d32680fafb67b5a6b5d0cd382b16d4e7b7bd0e49a753fedd
Tx prefix hash: 71bfa553b5d525aeb86e1a634d5135d9fcafedaaa4fa73fd4bca6c88af05b570
Tx public key: e71247a2aeb82c8c9122d645f8707691665d9eb58e441361a546c4b3c9860982
| Timestamp: 1779956551 | Timestamp [UTC]: 2026-05-28 08:22:31 | Age [y:d:h:m:s]: 00:016:02:39:45 |
| Block: 3700 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5045 | RingCT/type: yes/0 |
| Extra: 01e71247a2aeb82c8c9122d645f8707691665d9eb58e441361a546c4b3c986098202090000000226697be300 | ||
1 output(s) for total of 34.937009796623 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e1027bdf73475aba33cf4d77dfa3f5be3684419b988a943da3e386e278b40d0 | 34.937009796623 | 4476 of 0 | <96> |
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": 3760,
"vin": [ {
"gen": {
"height": 3700
}
}
],
"vout": [ {
"amount": 34937009796623,
"target": {
"tagged_key": {
"key": "5e1027bdf73475aba33cf4d77dfa3f5be3684419b988a943da3e386e278b40d0",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 231, 18, 71, 162, 174, 184, 44, 140, 145, 34, 214, 69, 248, 112, 118, 145, 102, 93, 158, 181, 142, 68, 19, 97, 165, 70, 196, 179, 201, 134, 9, 130, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}