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: 9495c8a8611c72814aaa0cbede4bb6dcb3a5820615bfeeff24511f94192de633
Tx prefix hash: d104f8a0a7d17c26a2f4d316156ba8a7367546dfc3d809bd147dae15d31ee2e7
Tx public key: 5e132b8b6a4a45bdb4fdce412afbbd3ecc25f7dd325e604ca0e3a9cdc7073c78
| Timestamp: 1779477410 | Timestamp [UTC]: 2026-05-22 19:16:50 | Age [y:d:h:m:s]: 00:025:13:19:24 |
| Block: 626 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8119 | RingCT/type: yes/0 |
| Extra: 015e132b8b6a4a45bdb4fdce412afbbd3ecc25f7dd325e604ca0e3a9cdc7073c7802090000000293369e7d00 | ||
1 output(s) for total of 35.142453999062 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a1338928692ecb5c3a4c79a505ee323bf3fd5065d6e3104d9bb0ff5463038d7 | 35.142453999062 | 654 of 0 | <8e> |
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": 686,
"vin": [ {
"gen": {
"height": 626
}
}
],
"vout": [ {
"amount": 35142453999062,
"target": {
"tagged_key": {
"key": "9a1338928692ecb5c3a4c79a505ee323bf3fd5065d6e3104d9bb0ff5463038d7",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 94, 19, 43, 139, 106, 74, 69, 189, 180, 253, 206, 65, 42, 251, 189, 62, 204, 37, 247, 221, 50, 94, 96, 76, 160, 227, 169, 205, 199, 7, 60, 120, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}