transaction
Transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
11aa95a2fc423618c1441f3f213c05aaa1b04cb645069c8a2ddb86226a7d1ee5Public counts derived from this transaction's structure. Shielded entries are counted, but their parties, amounts, and memos stay private.
| Input | Prevout | Value |
|---|---|---|
| vin 64 | transparent prevout | 0.00000066 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.
Per-transaction mempool event timelines (added → mined / invalidated / suppressed) are not yet exposed by the upstream detail RPC; until they are, follow the live feed at /mempool or subscribe to /api/v1/stream for source-observed events.
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.