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: 7a83db0d49453e820d150cb0fa082a57be79966c3707aa67f1b13b8a85ca29ab
Tx prefix hash: 72c1b8a703dd7356aa8a63ed9d6ab14c13b9cb29c2e4d200d60707b72b9286fc
Tx public key: b67acea4a575303edd985e3691dce0a5b1d90f4e2c4ee5e94918508b4f35b052
| Timestamp: 1779787830 | Timestamp [UTC]: 2026-05-26 09:30:30 | Age [y:d:h:m:s]: 00:013:19:02:32 |
| Block: 2191 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5836 | RingCT/type: yes/0 |
| Extra: 01b67acea4a575303edd985e3691dce0a5b1d90f4e2c4ee5e94918508b4f35b05202090000000126697be300 | ||
1 output(s) for total of 35.037710060668 HMNY
| stealth address | amount | amount idx | tag |
| 00: b269537a37b5efef3cd95fac1bda90f326e24c7c26a5e9936a435e54c00b1bd2 | 35.037710060668 | 2533 of 0 | <eb> |
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": 2251,
"vin": [ {
"gen": {
"height": 2191
}
}
],
"vout": [ {
"amount": 35037710060668,
"target": {
"tagged_key": {
"key": "b269537a37b5efef3cd95fac1bda90f326e24c7c26a5e9936a435e54c00b1bd2",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 182, 122, 206, 164, 165, 117, 48, 62, 221, 152, 94, 54, 145, 220, 224, 165, 177, 217, 15, 78, 44, 78, 229, 233, 73, 24, 80, 139, 79, 53, 176, 82, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}