transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
bdf636ad36a86f8ccab224d645fbb7003565367b6bda8fcb24a9e96765d4ac6bPublic 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 | 0.19980000 ZEC |
| vin 1 | transparent prevout | 1.68980000 ZEC |
| vin 2 | transparent prevout | 5.99980000 ZEC |
| vin 3 | transparent prevout | 1.69980000 ZEC |
| vin 4 | transparent prevout | 17.54173291 ZEC |
| vin 5 | transparent prevout | 2.57285068 ZEC |
| vin 6 | transparent prevout | 0.62980000 ZEC |
| vin 7 | transparent prevout | 20.99980000 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.
The actual fee can't be recovered because this transaction has Shielded inputs. The number below is the minimum recommended fee for a transaction this shape: a fair-share floor, not the amount paid.
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.