Trust starts with the label.
Where the browser gets its data, what “fetched” means, and why unavailable information never becomes a fabricated live statistic.
The live browser uses BlockCypher’s public Litecoin mainnet API. It does not run a full node, maintain an independent transaction index, or validate consensus proofs in the browser. A successful result is a named provider’s observation—not a claim that this website independently verified the chain.
When requests happen
Before you click “Load public data,” this package makes no API requests. After that click, a permission flag is kept for this tab’s session so that following a block, transaction, or address can load the relevant record. Static articles, navigation, and images do not require that permission or an API connection.
The provider receives ordinary request metadata, including your network connection information and the public identifiers requested. You can clear the session flag and cached results on the privacy page. Following a labeled external explorer link is a separate visit to that third-party service.
How freshness is reported
A fetch timestamp identifies when a response was obtained by the browser. It is separate from a block’s recorded timestamp and from a transaction’s provider-reported receipt time. Responses may be reused from the tab’s session cache for up to 90 seconds. The original fetch timestamp remains visible.
There is no automatic background polling or fabricated live stream. Manual refresh requests new data. A page left open can become old, so read the fetch label before relying on a confirmation count or chain height. Different providers can also lag or disagree.
What the interface covers
The browser presents chain information, recent blocks, block fields, transaction identifiers, supported transparent transaction inputs and outputs, and supported transparent address summaries. It also offers a small provider-observed mempool sample. The API documentation is the primary reference for the response fields.
Block identifiers are paginated. Transaction and address displays have explicit caps. An address balance is not a complete wallet balance; a transaction total may include change and several recipients. A provider’s peer count is not the global node count. Fee estimates are not confirmation guarantees.
What it does not infer
The site does not infer address ownership, identity, miner hardware ownership, market price, market capitalization, global hash rate, AuxPoW revenue, or confidential MWEB amounts from unrelated response fields. Unsupported information remains unavailable. Illustrations in the guides are labeled hypothetical and are never used as live explorer rows.
Errors remain errors
A provider timeout, a rate-limit response, a malformed identifier, and an empty valid result are different states. The client reports those distinctions. A failed request does not establish a zero balance, a failed payment, or an empty network mempool. Cross-origin browser access is also a provider dependency and can change.
For consequential verification, compare an independent source or an appropriately configured node. The Litecoin Core REST documentation explains a node-based access model. A receiving service’s private account credit still requires that service’s own records, even when an on-chain transaction is confirmed.
Editorial sources
The learning content uses primary protocol implementations, Litecoin improvement proposals, and provider documentation. Each long-form field note includes one directly relevant editorial source link. Browse the primary-source directory for the broader reference set and report specific corrections through Contact.