transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a0de6da9a54a80e6ec0f11347b362a76cf6120ed5aff22aa7291a808d9d5467fPublic 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 | 1.25750012 ZEC |
| vin 1 | transparent prevout | 1.25153331 ZEC |
| vin 2 | transparent prevout | 1.25180000 ZEC |
| vin 3 | transparent prevout | 1.25351046 ZEC |
| vin 4 | transparent prevout | 1.25010000 ZEC |
| vin 5 | transparent prevout | 1.25000000 ZEC |
| vin 6 | transparent prevout | 1.25117031 ZEC |
| vin 7 | transparent prevout | 1.25040000 ZEC |
| vin 8 | transparent prevout | 1.25020000 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.