Skip to content

Litecoin.watch · Research & practical tools

Litecoin research & data archive

Observed network data, downloadable samples and reproducible calculations. Every chart states what was measured and what it cannot tell you.

Collection began: 23 Sep 2026, 23:48 UTC. Network snapshots are scheduled every 15 minutes. This archive observes third-party APIs; it is not an independent Litecoin node.
Snapshots · last 30 days
7
Recorded block headers
129
Days with observations
2
Latest observed height
3,183,282

What we have observed

Transactions waiting in the provider's mempool

Mempool transaction counttransactions234023 Sep 23:0024 Sep 01:00 UTC
Mempool transaction count. Hourly means of available snapshots; breaks over one hour are left open. Download the underlying observations below.

Provider's rolling 24-hour average fee

Average transaction fee reported for the preceding 24 hoursLTC per transaction0.000042023 Sep 23:0024 Sep 01:00 UTC
Average transaction fee reported for the preceding 24 hours. Hourly means of available snapshots; breaks over one hour are left open. Download the underlying observations below.

These are overlapping snapshots. Averaging the displayed fee values does not produce a transaction-weighted fee for the whole period. A provider's mempool is one view of the network.

Block timestamp intervals

Differences between timestamps in adjacent recorded block headers. Miner-set timestamps are not stopwatch measurements of confirmation time.

Measure · last 30 days of available blocksObserved result
Valid adjacent intervals128
Median interval113.5 seconds
90th percentile405.6 seconds
Intervals longer than 10 minutes1
Missing heights inside the recorded range0
Negative timestamp differences excluded0
Observed block-hash replacements0

Each collection requests the latest 100 blocks. The initial window may include blocks mined before collection began; their first retrieval time is retained. Missing heights are excluded from adjacent-interval calculations. The most recent 100 heights are rechecked for changed hashes; deep reorganizations outside that window may be missed.

A reproducible fee-size experiment

How much does consolidating many inputs change the size of a standard native SegWit payment? The model below assumes P2WPKH inputs, two P2WPKH outputs and an illustrative fee rate of 1 litoshi/vB. This is a size calculation, not a live fee quote.

InputsEstimated vbytesModel fee · LTC
11410.00000141
107530.00000753
1006,8730.00006873
More inputs increase transaction size1 inputs14110 inputs753100 inputs6873
Estimated vbytes = ceil(10.5 + 68 × inputs + 31 × outputs). Actual signatures and transaction construction can change the result.

What this archive does not measure yet

We do not publish first-seen-to-confirmation timings. That study needs a consistently running observer, a documented transaction sample and a record of transactions that never confirm within the study window. Block timestamps alone cannot answer it.

MWEB private transfer amounts, individual users and merchant sales are not inferred from these snapshots. Missing values remain missing.