transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
0934d076c17890623c63d852ddefb70a44e7ccde2ceb3985035c780f182477f8Public 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.02329333 ZEC |
| vin 1 | transparent prevout | 0.02326689 ZEC |
| vin 2 | transparent prevout | 0.02289611 ZEC |
| vin 3 | transparent prevout | 0.02270892 ZEC |
| vin 4 | transparent prevout | 0.02262606 ZEC |
| vin 5 | transparent prevout | 0.02256547 ZEC |
| vin 6 | transparent prevout | 0.02251876 ZEC |
| vin 7 | transparent prevout | 0.02246187 ZEC |
| vin 8 | transparent prevout | 0.00686282 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.