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: 06a7f9fe275d508e03a1246916d286265d8166c34b2e3fd7c10561b1ed380687
Tx prefix hash: afd8986237bf6730b0cc3710deac189520c10be24ca735771882c3526f255d70
Tx public key: 1f3635ffea3fb05def90b7596b1d5a69289d7daf8c63e6e57c9f8e3b0c6afc58
| Timestamp: 1780726071 | Timestamp [UTC]: 2026-06-06 06:07:51 | Age [y:d:h:m:s]: 00:002:17:11:02 |
| Block: 6273 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1613 | RingCT/type: yes/0 |
| Extra: 011f3635ffea3fb05def90b7596b1d5a69289d7daf8c63e6e57c9f8e3b0c6afc58020900000001e49593ff00 | ||
1 output(s) for total of 34.765972518849 HMNY
| stealth address | amount | amount idx | tag |
| 00: f60be872ed9aa8e67af8d47b7bdff30c9ed87f2d5b71956fc97207399319a9e2 | 34.765972518849 | 7756 of 0 | <ed> |
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": 6333,
"vin": [ {
"gen": {
"height": 6273
}
}
],
"vout": [ {
"amount": 34765972518849,
"target": {
"tagged_key": {
"key": "f60be872ed9aa8e67af8d47b7bdff30c9ed87f2d5b71956fc97207399319a9e2",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 31, 54, 53, 255, 234, 63, 176, 93, 239, 144, 183, 89, 107, 29, 90, 105, 40, 157, 125, 175, 140, 99, 230, 229, 124, 159, 142, 59, 12, 106, 252, 88, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}