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: 8d22dc1c5d6da03ca30ff5aa8efa67e8b0af1d7d198bf9d84b2357701afc3e14
Tx prefix hash: c0c9013783ca1ba164b4e7effce2e8fb2e54a31fbf1c30d89fe78653e00e9053
Tx public key: eacee83d3f1d17e63efcf3f68ceeb0590df0542f5f62c84aae4fdf2c5c7c4116
| Timestamp: 1781003764 | Timestamp [UTC]: 2026-06-09 11:16:04 | Age [y:d:h:m:s]: 00:000:05:52:59 |
| Block: 8497 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 234 | RingCT/type: yes/0 |
| Extra: 01eacee83d3f1d17e63efcf3f68ceeb0590df0542f5f62c84aae4fdf2c5c7c4116020900000001e49593ff00 | ||
1 output(s) for total of 34.618809441636 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb1282d04ac9949a3a067c5f8e20e588a52914cc608c6a336544ec62a0011505 | 34.618809441636 | 10497 of 0 | <d4> |
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": 8557,
"vin": [ {
"gen": {
"height": 8497
}
}
],
"vout": [ {
"amount": 34618809441636,
"target": {
"tagged_key": {
"key": "eb1282d04ac9949a3a067c5f8e20e588a52914cc608c6a336544ec62a0011505",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 234, 206, 232, 61, 63, 29, 23, 230, 62, 252, 243, 246, 140, 238, 176, 89, 13, 240, 84, 47, 95, 98, 200, 74, 174, 79, 223, 44, 92, 124, 65, 22, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}