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: 4659baac6dd624f1f8a7f809060bf062156d8c07fa33fcebf5a2aa77358a8b9a
Tx prefix hash: 245ee52de8d73f704ecc0e8fc06729b02c6ad8c0b69f6b9b008f5a5b7bf86bf0
Tx public key: 6aac0f33fe0ad43cbd4c263a75cce43b6679e2516084aaee1d39355a8ae19d90
| Timestamp: 1780691966 | Timestamp [UTC]: 2026-06-05 20:39:26 | Age [y:d:h:m:s]: 00:003:04:07:21 |
| Block: 5764 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2122 | RingCT/type: yes/0 |
| Extra: 016aac0f33fe0ad43cbd4c263a75cce43b6679e2516084aaee1d39355a8ae19d90020900000001e49593ff00 | ||
1 output(s) for total of 34.799741152926 HMNY
| stealth address | amount | amount idx | tag |
| 00: 41980b2f529c74ee538b4fad6d450d29793ae541a04ca24d6e2ad5c564216ff9 | 34.799741152926 | 7217 of 0 | <57> |
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": 5824,
"vin": [ {
"gen": {
"height": 5764
}
}
],
"vout": [ {
"amount": 34799741152926,
"target": {
"tagged_key": {
"key": "41980b2f529c74ee538b4fad6d450d29793ae541a04ca24d6e2ad5c564216ff9",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 106, 172, 15, 51, 254, 10, 212, 60, 189, 76, 38, 58, 117, 204, 228, 59, 102, 121, 226, 81, 96, 132, 170, 238, 29, 57, 53, 90, 138, 225, 157, 144, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}