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: d66b8b67278d84fc800d544e9bd4d65f2b2b32503febd1c705e96f6fa2eaf942
Tx prefix hash: a50205c762994763f28032fa1f165f7493f1c504b450ae0f099aa275d05530a8
Tx public key: 103d0e81439ed1864bbdcf0fdd0e10b2db690471c4d462de918b2f36341293a5
| Timestamp: 1779631810 | Timestamp [UTC]: 2026-05-24 14:10:10 | Age [y:d:h:m:s]: 00:023:18:26:04 |
| Block: 925 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7820 | RingCT/type: yes/0 |
| Extra: 01103d0e81439ed1864bbdcf0fdd0e10b2db690471c4d462de918b2f36341293a5020900000002ba6d17be00 | ||
1 output(s) for total of 35.122418049155 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70d7072e40cda524e9ed22d00c5cad28da7bb3776784666dc31b2057563315da | 35.122418049155 | 1059 of 0 | <e9> |
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": 985,
"vin": [ {
"gen": {
"height": 925
}
}
],
"vout": [ {
"amount": 35122418049155,
"target": {
"tagged_key": {
"key": "70d7072e40cda524e9ed22d00c5cad28da7bb3776784666dc31b2057563315da",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 16, 61, 14, 129, 67, 158, 209, 134, 75, 189, 207, 15, 221, 14, 16, 178, 219, 105, 4, 113, 196, 212, 98, 222, 145, 139, 47, 54, 52, 18, 147, 165, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}