transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
f46e9a0a26c77029d1d8688e31de28cb37f0548778256d59753ac43d6491a3c7Public 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 | 14.15835877 ZEC |
| vin 1 | transparent prevout | 16.10000000 ZEC |
| vin 2 | transparent prevout | 18.32284669 ZEC |
| vin 3 | transparent prevout | 14.06381519 ZEC |
| vin 4 | transparent prevout | 14.98389532 ZEC |
| vin 5 | transparent prevout | 16.06728800 ZEC |
| vin 6 | transparent prevout | 15.17540400 ZEC |
| vin 7 | transparent prevout | 13.87415116 ZEC |
| vin 8 | transparent prevout | 14.99550000 ZEC |
| vin 9 | transparent prevout | 17.57000000 ZEC |
| vin 10 | transparent prevout | 13.88019056 ZEC |
| vin 11 | transparent prevout | 15.85345547 ZEC |
| vin 12 | transparent prevout | 14.49683468 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.