transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
696d6ed4ba767d4de20368870043a57deefc45b05c30a362ca31c84341acab20Public 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 | 67.99000000 ZEC |
| vin 1 | transparent prevout | 3579.99443063 ZEC |
| vin 2 | transparent prevout | 27.60480568 ZEC |
| vin 3 | transparent prevout | 29.41382002 ZEC |
| vin 4 | transparent prevout | 26.27079251 ZEC |
| vin 5 | transparent prevout | 24.88322937 ZEC |
| vin 6 | transparent prevout | 25.50517236 ZEC |
| vin 7 | transparent prevout | 27.84699129 ZEC |
| vin 8 | transparent prevout | 28.81226289 ZEC |
| vin 9 | transparent prevout | 25.18443260 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.