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: c63ae827f0accf7bea881d28c90b48cfba17c40139fff7dfc6e035d231d1ce98
Tx prefix hash: b2756c31d8176961284dfa6a90c0331c0c40b7cf1be0578234a79bf13a046269
Tx public key: 0ffc6098814039dfd3becd945e03e401937b7d0f8644f8735eb9d35e9003feb9
| Timestamp: 1779437300 | Timestamp [UTC]: 2026-05-22 08:08:20 | Age [y:d:h:m:s]: 00:017:19:30:30 |
| Block: 160 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7786 | RingCT/type: yes/0 |
| Extra: 010ffc6098814039dfd3becd945e03e401937b7d0f8644f8735eb9d35e9003feb9020900000001a662ed0300 | ||
1 output(s) for total of 35.173703387217 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f6e553d6ae8e72c94de2c58fd8b6c8fe2ae20ec1c783409e274a04516daf171 | 35.173703387217 | 156 of 0 | <aa> |
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": 220,
"vin": [ {
"gen": {
"height": 160
}
}
],
"vout": [ {
"amount": 35173703387217,
"target": {
"tagged_key": {
"key": "8f6e553d6ae8e72c94de2c58fd8b6c8fe2ae20ec1c783409e274a04516daf171",
"view_tag": "aa"
}
}
}
],
"extra": [ 1, 15, 252, 96, 152, 129, 64, 57, 223, 211, 190, 205, 148, 94, 3, 228, 1, 147, 123, 125, 15, 134, 68, 248, 115, 94, 185, 211, 94, 144, 3, 254, 185, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}