Privacy has scope. So does an explorer.

Mimblewimble Extension Blocks, or MWEB, use an extension-block design with confidentiality features. Their records should not be forced into the same model as an ordinary transparent address-history table. A general explorer cannot promise to reveal information it does not possess.

The design and the data are different questions

Litecoin Improvement Proposal 3 describes the technical extension-block design. Understanding that design is one task. Establishing which fields a particular API indexes and returns is another. A provider can lack support even for information that is otherwise publicly observable.

This site’s read-only browser does not offer confidential MWEB balance lookups, private amount recovery, or complete MWEB transaction histories. Its learning resources explain those boundaries; the interface does not replace missing coverage with invented values.

Confidential does not mean every context disappears

A privacy feature protects specified information under particular assumptions. It does not erase everything a wallet, receiving service, or counterparty may know from the transaction workflow. Information shared outside the blockchain can also affect privacy. Ask who can see which details, rather than treating “private” as an unlimited guarantee.

A wallet’s view and a public explorer’s view may legitimately differ. The wallet can hold information relevant to its own activity that an outside observer does not have. Compare their scope before concluding that a missing explorer entry means funds are missing.

Unsupported is not zero

A timeout, an unrecognized record type, and a measured zero balance are different results. This browser preserves that distinction. It will not label confidential data as zero simply because its transparent-address provider cannot supply the requested view.

Read the data-source methodology before interpreting a provider response. For wallet or receiving-service support, use authenticated documentation and check current feature restrictions. The existence of a network capability does not guarantee that every service supports every related transaction type.

Keep spending secrets out of support requests

Do not give an explorer your private keys, recovery words, or wallet backup to “reveal” a transaction. Public-data inspection and importing spending authority are very different activities. Use the minimum information needed to investigate through trusted channels.

The full MWEB visibility guide explores public observations, wallet knowledge, support limitations, and ways to evaluate privacy claims without overstating what any one tool can prove.