transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
71db9e8c0c968d505847e4f47afc0c6504fd86c43e1581233841c6b8725e8c12Public 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 | 8.77152393 ZEC |
| vin 1 | transparent prevout | 6.28975766 ZEC |
| vin 2 | transparent prevout | 11.27393168 ZEC |
| vin 3 | transparent prevout | 12.52557062 ZEC |
| vin 4 | transparent prevout | 0.01003296 ZEC |
| vin 5 | transparent prevout | 0.05858951 ZEC |
| vin 6 | transparent prevout | 0.12800968 ZEC |
| vin 7 | transparent prevout | 2.50992065 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.