transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a948ff68097d5def04c3a0a89ca0573af857d5912811319fac8fff8cfb0252c6Public 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 | 8.95830876 ZEC |
| vin 1 | transparent prevout | 2.21729230 ZEC |
| vin 2 | transparent prevout | 1.98980387 ZEC |
| vin 3 | transparent prevout | 1.16833671 ZEC |
| vin 4 | transparent prevout | 0.49720193 ZEC |
| vin 5 | transparent prevout | 0.29847685 ZEC |
| vin 6 | transparent prevout | 0.21878610 ZEC |
| vin 7 | transparent prevout | 0.11305574 ZEC |
| vin 8 | transparent prevout | 0.11100882 ZEC |
| vin 9 | transparent prevout | 0.10611056 ZEC |
| vin 10 | transparent prevout | 0.05000000 ZEC |
| vin 11 | transparent prevout | 0.03771914 ZEC |
| vin 12 | transparent prevout | 0.02000000 ZEC |
| vin 13 | transparent prevout | 0.01228526 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.