Sources, methods & corrections

Three kinds of evidence

Network archive

The scheduled collector requests Blockchair Litecoin and Dogecoin statistics every 15 minutes. It retains the provider's source timestamp separately from our retrieval time. Repeated source timestamps are deduplicated; unsuccessful attempts are logged and do not create observations.

Snapshot fields include block height, reported mempool count, rolling 24-hour average transaction fee, estimated hashrate, difficulty and the provider's USD reference price. Dogecoin price and difficulty support reproducible merged-mining calculations; a failed Dogecoin read leaves those fields empty. Hashrate is the provider's estimate, not directly measured hardware output.

Fresh snapshots must have source timestamps no more than 15 minutes old and a reported tip block no more than 30 minutes old. This conservative rule can reject a valid network during a long block gap; it does not imply a network outage. All archive exports use Unix seconds in UTC. Litecoin fee amounts are LTC unless a column explicitly says litoshi; 100,000,000 litoshis equal 1 LTC.

The rolling fee series is not a fee recommendation. Consecutive 24-hour windows overlap. The chart uses hourly means of available snapshots and leaves long gaps open. Its zero baseline is shown; the collection log and CSV expose missing observations.

We request the latest 100 blocks each run and recheck those heights for changed hashes. Block records include first retrieval and last check times. Replacements are counted as observed revisions, not attributed to a cause. Deep reorganizations outside the checked window may be missed. Original block timestamps can predate the archive.

Interval statistics compare adjacent recorded heights only. Negative timestamp differences are counted separately and excluded; zero differences remain. Quantiles use linear interpolation at index (n − 1) × q on the sorted sample. These are miner-set timestamp differences, not first-seen-to-confirmation durations.

Blockchair API documentation · Observations · Run log · Reproduction script

Transaction checker

The form accepts a public 64-character transaction ID. Our server asks Blockchair's Litecoin transaction dashboard and displays a limited summary. Confirmations are calculated as provider tip height − transaction block height + 1 for a confirmed record.

Virtual size is ceil(weight / 4). The effective fee rate is fee in litoshis / virtual size. Coinbase and identified MWEB-related records receive a separate explanation; their rate is not interpreted as a standard payment fee. A not-found response describes this source, not every node or a wallet's private MWEB state.

Transaction IDs travel in a POST body, not a page URL. The tool does not save search history in the browser and does not load Google Analytics. The server keeps a limited summary cache for two minutes. Rate-limit counters use a daily keyed hash of the connecting IP and expire; normal hosting access logs can still record a visit. Requests to the data provider expose the public ID to that provider. No recovery secrets are requested.

Weekly reports

Reports summarize completed UTC weeks, Monday 00:00 through the next Monday 00:00. A report requires at least one valid observation on all seven days. The report shows actual counts and expected 15-minute collection slots, so a week with gaps is visible. Figures are generated from the archived data using the formulas above; they are not manually inferred market commentary.

A frozen report records its generation time. Its CSV source archive may later reflect a rechecked block. Any material correction to a published report will be explained rather than silently presented as a new measurement.

Editorial responsibility and dates

Article bylines identify the named author or responsible editor shown on that article. An edited date means the record changed; it does not certify that every statement was independently reviewed. Where a fact-check record exists, the article shows its date and scope separately. We do not invent reviewers or attach expertise claims to an automated check.

Research pages distinguish calculations, public-source observations and actual software tests. A documentation review does not become a hands-on test. Recovery phrases, private keys and private wallet exports are never appropriate evidence to publish.

Material corrections should state what was wrong, what changed and when. Report an issue through the contact page, including the page URL and the relevant source or calculation. View the public corrections log.

Commercial links and related sites

The wallet comparison introduced here uses direct documentation links without affiliate tracking and does not sell ranking positions. Its order is not a recommendation or a security score. Sponsored material and affiliate links must be disclosed where they appear.

Links to related projects such as Forex Mechanics and Currency Converter are included only when they help with the task and are identified as related projects. A cross-link is not independent corroboration of a claim.