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: 941ea6aee3ce4f0826e3e592cbdee10c7f29782c2969d6c33cbb634fd87fd74c
Tx prefix hash: 3963b337117bcf727539d2bda3fc1ce002d2f4d52b1024f94a4f4cbc8ae279b3
Tx public key: 0439562ae1e698a10c571ac3826722f46cc1cf7762aac46c6a0cc3f4faccac3a
| Timestamp: 1780981912 | Timestamp [UTC]: 2026-06-09 05:11:52 | Age [y:d:h:m:s]: 00:000:09:37:03 |
| Block: 8052 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 603 | RingCT/type: yes/0 |
| Extra: 010439562ae1e698a10c571ac3826722f46cc1cf7762aac46c6a0cc3f4faccac3a020900000001e49593ff00 | ||
1 output(s) for total of 34.648205354884 HMNY
| stealth address | amount | amount idx | tag |
| 00: a5909353e1856b467065cf9649d4922152878b1946c9f524f8bea53b19728037 | 34.648205354884 | 9980 of 0 | <26> |
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": 8112,
"vin": [ {
"gen": {
"height": 8052
}
}
],
"vout": [ {
"amount": 34648205354884,
"target": {
"tagged_key": {
"key": "a5909353e1856b467065cf9649d4922152878b1946c9f524f8bea53b19728037",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 4, 57, 86, 42, 225, 230, 152, 161, 12, 87, 26, 195, 130, 103, 34, 244, 108, 193, 207, 119, 98, 170, 196, 108, 106, 12, 195, 244, 250, 204, 172, 58, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}