transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
8fb54eb704648baf0f7c7e8f6a0118d651d0e5e3c04e95e4b8f8f8e267fa6ca3Public 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 | 40.76491414 ZEC |
| vin 1 | transparent prevout | 307.84471620 ZEC |
| vin 2 | transparent prevout | 42.24223641 ZEC |
| vin 3 | transparent prevout | 3110.20713986 ZEC |
| vin 4 | transparent prevout | 230.69312248 ZEC |
| vin 5 | transparent prevout | 127.54532228 ZEC |
| vin 6 | transparent prevout | 34.53702007 ZEC |
| vin 7 | transparent prevout | 300.27079395 ZEC |
| vin 8 | transparent prevout | 294.04306718 ZEC |
| vin 9 | transparent prevout | 167.76119828 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.