transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
be4f1bf67d604e58f3a1019deed538ce94c07a4212f8a7a70d772553ed9ef1d0Public 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 | 2265.89484699 ZEC |
| vin 1 | transparent prevout | 1009.85200427 ZEC |
| vin 2 | transparent prevout | 179.07030021 ZEC |
| vin 3 | transparent prevout | 158.86877757 ZEC |
| vin 4 | transparent prevout | 145.34234307 ZEC |
| vin 5 | transparent prevout | 137.58334924 ZEC |
| vin 6 | transparent prevout | 0.00440000 ZEC |
| vin 7 | transparent prevout | 0.00360000 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.