The public headers tell a more precise story than “’s first week”. We queried heights 0 through 1,000 from our . Height 3 records 13 October 2011 at 02:59:41 UTC; height 1,000 records 03:47:07 UTC that same day. That is a difference of 47 minutes 26 seconds in their recorded times.
Those timestamps are miner-supplied header fields, not an independent stopwatch. Eight adjacent differences in heights 3–1,000 run backwards and 43 are zero. Treating every difference as a real observed block-production interval would turn the defects of that clock into a false performance benchmark.
Correction, 2 October 2026: the previous narrative attributed miner shares, geographic distribution and coin dormancy without an underlying dataset. We replaced those claims with 1,001 inspectable headers and a separate, explicitly bounded unspent-output study.
The four early timestamps that a history needs to separate
| Height | Recorded header time, UTC | Transactions |
|---|---|---|
| 0 | 2011-10-07 07:31:05 | 1 |
| 1 | 2011-10-08 06:29:19 | 1 |
| 2 | 2011-10-12 02:34:18 | 1 |
| 3 | 2011-10-13 02:59:41 | 1 |
| 448 | 2011-10-13 03:22:57 | 2 |
| 458 | 2011-10-13 03:23:32 | 2 |
| 1,000 | 2011-10-13 03:47:07 | 1 |
The genesis timestamp, the next two headers and the dense sequence beginning at height 3 describe different points. A genesis date is not a count of active miners or proof that public production was already proceeding at a stable rate. The Foundation’s historical account provides launch context; our header export answers the narrower numerical question.
Count first, interpret second
| Statistic | Result |
|---|---|
| Headers in this dense segment | 998 |
| Adjacent signed differences | 997 |
| Negative differences | 8 |
| Zero differences | 43 |
| Median signed difference | 3 seconds |
| 90th percentile signed difference | 5 seconds |
| Full height 0–1,000 sample: one-transaction blocks | 999 |
| Full sample: two-transaction blocks | 2: heights 448 and 458 |
The median and percentile describe signed differences exactly as recorded, including the negatives. They do not mean the network reliably delivered a block to every three seconds. We do not remove inconvenient clock values or relabel them as zero.
The sample also distinguishes transaction counts from payment activity. A one-transaction early block contains its . Two transactions in a block do not prove two customer payments. Headers do not provide a count of people or businesses using Litecoin.
Can these headers identify early miners?
No. A hash, timestamp and transaction count cannot identify a person. A miner-share study needs complete coinbase data, a disclosed clustering rule and validation of any attribution. Different addresses can belong to one operator; a shared pool can represent many miners. We have not performed that study here.
Likewise, block count times a 50 LTC subsidy is a permitted-issuance calculation, not proof that every output remains unspent or belongs to the same owner. Our check of 998 early output-zero outpoints answers a different question with a current snapshot.
How to reproduce the header reconstruction
The capture uses getblockhash and getblockheader against a pruned Litecoin Core node. Old headers remain available even when old block bodies have been pruned. Each row records height, block hash, timestamp, transaction count and the reported difficulty. Block identities were rechecked at the end of collection.
Another node can check selected heights independently. Recalculating our downloaded CSV proves only that the table and chart follow the captured values. It is valuable, but it is a different level of verification from acquiring the headers independently.
Use the right clock for the question
Header times are useful for historical reconstruction when their limitations stay visible. For present payment waiting times, use polling timestamps: What our node has observed about Litecoin confirmation times so far. For future issuance, use and the integer subsidy schedule. Neither a fast launch sequence nor today’s block arrival predicts the price.
Check the result yourself
The versioned package keeps its capture boundary. It will not silently become a live quote. Download the files into one folder and run python analyze.py.txt .. The script validates input hashes before calculating the published results. A successful rerun checks the arithmetic on this export; it does not independently validate our node or prove that the sample represents the whole network.
Sources and review scope
Reviewed against the linked materials on 2 October 2026. Calculations and drafting were AI-assisted; no independent external review or personal attendance is claimed. Original publication date retained. See our corrections policy.
