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: 36cb489e3274703e80f7ea60c44210c0f54d7c90b2cb3011bc694e4ed22401fa
Tx prefix hash: 12009672ca7306260cb5928ec0387da4246a9a803f2ff19a72d12fdda3a561b5
Tx public key: c96d30f7c9c17ca245c361afeb3c3c644efd378d1e4ada082e8c2b17b38bd269
| Timestamp: 1779772696 | Timestamp [UTC]: 2026-05-26 05:18:16 | Age [y:d:h:m:s]: 00:013:21:22:20 |
| Block: 2033 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5863 | RingCT/type: yes/0 |
| Extra: 01c96d30f7c9c17ca245c361afeb3c3c644efd378d1e4ada082e8c2b17b38bd26902090000000126697be300 | ||
1 output(s) for total of 35.058050664221 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f1ef53e922449a47e68c9d08ced032352d4ca694f4e9baa026bf3f1ba9f3057 | 35.058050664221 | 2323 of 0 | <23> |
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": 2093,
"vin": [ {
"gen": {
"height": 2033
}
}
],
"vout": [ {
"amount": 35058050664221,
"target": {
"tagged_key": {
"key": "9f1ef53e922449a47e68c9d08ced032352d4ca694f4e9baa026bf3f1ba9f3057",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 201, 109, 48, 247, 201, 193, 124, 162, 69, 195, 97, 175, 235, 60, 60, 100, 78, 253, 55, 141, 30, 74, 218, 8, 46, 140, 43, 23, 179, 139, 210, 105, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}