transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a1f915ebfd838223d5f113b8bd45e68360115ce141ef05c0207a2d39322617f1Public counts derived from this transaction's structure. Shielded entries are counted, but their parties, amounts, and memos stay private.
| Input | Prevout | Value |
|---|---|---|
| vin 0 | transparent prevout | 0.10986964 ZEC |
| vin 1 | transparent prevout | 0.10950536 ZEC |
| vin 2 | transparent prevout | 0.10804032 ZEC |
| vin 3 | transparent prevout | 0.10726647 ZEC |
| vin 4 | transparent prevout | 0.10526058 ZEC |
| vin 5 | transparent prevout | 0.10492995 ZEC |
| vin 6 | transparent prevout | 0.10350308 ZEC |
| vin 7 | transparent prevout | 0.10310806 ZEC |
| vin 8 | transparent prevout | 0.10050957 ZEC |
| vin 9 | transparent prevout | 0.10033645 ZEC |
| vin 10 | transparent prevout | 0.10029616 ZEC |
| vin 11 | transparent prevout | 0.10028684 ZEC |
Input values are read from the upstream prevout index. When a value is unavailable, the upstream has not finished resolving the spent outpoint; the input still exists, but its zatoshi amount is not yet cached. Transparent outputs and full script bodies are scheduled for a follow-up consumer integration phase.
Actual fee paid by this transaction, recovered by looking up its transparent inputs. The minimum recommended fee is shown alongside for context.
Zexplorer never knows whether you sent or received any shielded portion of this transaction. If a payer provided a ZIP-311 payment disclosure, you can verify it against the public chain facts above. Disclosure payloads are processed once, never persisted, and never logged.
verify a payment disclosure →Disclosure verification is capability-gated on the upstream node (explorer.payment_disclosure.verify_v1). The tool will show an explicit "unavailable on this node" state when the operator hasn't enabled the verifier.