transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a1e2a8017542c090964cb2040fe5da77ba55e6fa71173bf02aa8df6211f1ae9bPublic 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 | 7.89525981 ZEC |
| vin 1 | transparent prevout | 0.22722975 ZEC |
| vin 2 | transparent prevout | 0.12783375 ZEC |
| vin 3 | transparent prevout | 0.12273525 ZEC |
| vin 4 | transparent prevout | 0.11870099 ZEC |
| vin 5 | transparent prevout | 0.11372624 ZEC |
| vin 6 | transparent prevout | 0.10526159 ZEC |
| vin 7 | transparent prevout | 0.10399947 ZEC |
| vin 8 | transparent prevout | 0.10137570 ZEC |
| vin 9 | transparent prevout | 0.10273740 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.