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: d34ca866cf4281d1462cd3f17e8df800ba8c9fdf069710054e673106995331a0
Tx prefix hash: ff945cad75940eea9c91ac584e0987be916ede7c92ba3d92b37a078888870805
Tx public key: 9a98ae81c9111c9f2e7ac9e09b4b9bc86253ba08310a6f427d56b0d755f0c133
| Timestamp: 1780691233 | Timestamp [UTC]: 2026-06-05 20:27:13 | Age [y:d:h:m:s]: 00:009:11:52:22 |
| Block: 5716 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3029 | RingCT/type: yes/0 |
| Extra: 019a98ae81c9111c9f2e7ac9e09b4b9bc86253ba08310a6f427d56b0d755f0c133020900000001e49593ff00 | ||
1 output(s) for total of 34.802927313271 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c22239df09bad5a05590bcc2915cd07e32598608199be1afb978805013b046d | 34.802927313271 | 7167 of 0 | <87> |
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": 5776,
"vin": [ {
"gen": {
"height": 5716
}
}
],
"vout": [ {
"amount": 34802927313271,
"target": {
"tagged_key": {
"key": "9c22239df09bad5a05590bcc2915cd07e32598608199be1afb978805013b046d",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 154, 152, 174, 129, 201, 17, 28, 159, 46, 122, 201, 224, 155, 75, 155, 200, 98, 83, 186, 8, 49, 10, 111, 66, 125, 86, 176, 215, 85, 240, 193, 51, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}