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: 8698746d807d419c08ccc97fca46327cdd2307fa0dbf72a15fa5fa4a0f3e8160
Tx prefix hash: d575d149c735d61691375c078125429034b2139a6477d1ab680a734975e41763
Tx public key: fb1a64793b12bf127ff21b42afd665803b4b0ae195addb94170bc1b710eb8999
| Timestamp: 1779991531 | Timestamp [UTC]: 2026-05-28 18:05:31 | Age [y:d:h:m:s]: 00:011:06:41:16 |
| Block: 3996 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3890 | RingCT/type: yes/0 |
| Extra: 01fb1a64793b12bf127ff21b42afd665803b4b0ae195addb94170bc1b710eb899902090000000126697be300 | ||
1 output(s) for total of 34.917290775646 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5ab1e50092a9366b017d163aab44c55d70078d4eadadf8e84426c619347a24c | 34.917290775646 | 4936 of 0 | <3e> |
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": 4056,
"vin": [ {
"gen": {
"height": 3996
}
}
],
"vout": [ {
"amount": 34917290775646,
"target": {
"tagged_key": {
"key": "c5ab1e50092a9366b017d163aab44c55d70078d4eadadf8e84426c619347a24c",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 251, 26, 100, 121, 59, 18, 191, 18, 127, 242, 27, 66, 175, 214, 101, 128, 59, 75, 10, 225, 149, 173, 219, 148, 23, 11, 193, 183, 16, 235, 137, 153, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}