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: e397d13675a8d75d4f05c046f314bda9f8fdc8df1bc8e9699fd3198e773ba13c
Tx prefix hash: 73ab3ad72ebe3fbb80c11154e04ed035df36c699195e3d36a33a210ab2995daa
Tx public key: e67540c366ea6750bd4d766a47e0c2faf890dae985d7b0cf6ed685a73854305c
| Timestamp: 1780058200 | Timestamp [UTC]: 2026-05-29 12:36:40 | Age [y:d:h:m:s]: 00:010:14:13:08 |
| Block: 4483 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3424 | RingCT/type: yes/0 |
| Extra: 01e67540c366ea6750bd4d766a47e0c2faf890dae985d7b0cf6ed685a73854305c02090000000526697be300 | ||
1 output(s) for total of 34.884871873073 HMNY
| stealth address | amount | amount idx | tag |
| 00: c936ffe9c77f0f509f29f43147c8d871750dfd069b250da6c338af78587365e2 | 34.884871873073 | 5616 of 0 | <1b> |
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": 4543,
"vin": [ {
"gen": {
"height": 4483
}
}
],
"vout": [ {
"amount": 34884871873073,
"target": {
"tagged_key": {
"key": "c936ffe9c77f0f509f29f43147c8d871750dfd069b250da6c338af78587365e2",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 230, 117, 64, 195, 102, 234, 103, 80, 189, 77, 118, 106, 71, 224, 194, 250, 248, 144, 218, 233, 133, 215, 176, 207, 110, 214, 133, 167, 56, 84, 48, 92, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}