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: 1aaa813a30a23371c91da8c03e631ae78a410a72747734024c4edaf8e4896167
Tx prefix hash: 95cf86de1e60f4fb2be1ad3e5d80dba776092d81b6a81fb3c5f8f307002aeebf
Tx public key: db60c0ed03c34e89ba913008778424df36ac987808c88a8369e3a1d02031a4d3
| Timestamp: 1779970909 | Timestamp [UTC]: 2026-05-28 12:21:49 | Age [y:d:h:m:s]: 00:011:16:11:13 |
| Block: 3846 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4186 | RingCT/type: yes/0 |
| Extra: 01db60c0ed03c34e89ba913008778424df36ac987808c88a8369e3a1d02031a4d302090000000126697be300 | ||
1 output(s) for total of 34.927282131405 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d7c564aac31825692dbad2f42b8c5cbd1715ca19076206b06d7ed119fdf59a6 | 34.927282131405 | 4695 of 0 | <e0> |
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": 3906,
"vin": [ {
"gen": {
"height": 3846
}
}
],
"vout": [ {
"amount": 34927282131405,
"target": {
"tagged_key": {
"key": "6d7c564aac31825692dbad2f42b8c5cbd1715ca19076206b06d7ed119fdf59a6",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 219, 96, 192, 237, 3, 195, 78, 137, 186, 145, 48, 8, 119, 132, 36, 223, 54, 172, 152, 120, 8, 200, 138, 131, 105, 227, 161, 208, 32, 49, 164, 211, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}