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: e7b538a82f96b86fbeddb2b63580597bef9c181aa449f9bb522c06f02eb6ee93
Tx prefix hash: 4c0429ec30ca069503db743ff52297a92b9e3e17aa5b25859b59770989153fda
Tx public key: 63d38469890a93972e6cfe6d83d9a619ee3e2ceb7997896d7916ddad7c598731
| Timestamp: 1780686576 | Timestamp [UTC]: 2026-06-05 19:09:36 | Age [y:d:h:m:s]: 00:003:08:29:14 |
| Block: 5433 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2509 | RingCT/type: yes/0 |
| Extra: 0163d38469890a93972e6cfe6d83d9a619ee3e2ceb7997896d7916ddad7c598731020900000001e49593ff00 | ||
1 output(s) for total of 34.864363914615 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29d86e9b9423dca8491fe14c21de8c42cdeeb0f1eefbacfc5c7d0b85ec51f2a5 | 34.864363914615 | 6870 of 0 | <e1> |
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": 5493,
"vin": [ {
"gen": {
"height": 5433
}
}
],
"vout": [ {
"amount": 34864363914615,
"target": {
"tagged_key": {
"key": "29d86e9b9423dca8491fe14c21de8c42cdeeb0f1eefbacfc5c7d0b85ec51f2a5",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 99, 211, 132, 105, 137, 10, 147, 151, 46, 108, 254, 109, 131, 217, 166, 25, 238, 62, 44, 235, 121, 151, 137, 109, 121, 22, 221, 173, 124, 89, 135, 49, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}