transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
c3771e35946704625c1eec5e53ffefa3abab05f97e2d180f4fa1d689cc653f64Public 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.01978944 ZEC |
| vin 1 | transparent prevout | 0.01822476 ZEC |
| vin 2 | transparent prevout | 0.01818682 ZEC |
| vin 3 | transparent prevout | 0.01808414 ZEC |
| vin 4 | transparent prevout | 0.01363662 ZEC |
| vin 5 | transparent prevout | 0.01056441 ZEC |
| vin 6 | transparent prevout | 0.01055377 ZEC |
| vin 7 | transparent prevout | 0.01047040 ZEC |
| vin 8 | transparent prevout | 0.01036664 ZEC |
| vin 9 | transparent prevout | 0.01032406 ZEC |
| vin 10 | transparent prevout | 0.01017966 ZEC |
| vin 11 | transparent prevout | 0.01016695 ZEC |
| vin 12 | transparent prevout | 0.01007519 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.