Litecoin on-chain data

A source-stamped network snapshot and the observations we have collected. Use the history to investigate a change; use a transaction record to check a payment.

Current network snapshot

Current · Blockchair network statistics

Within our source-time and block-time freshness limits.

Source snapshot: Provider fetched: Observed tip timestamp:
Check collection status

Refreshing the page is not a new blockchain observation. While visible, this view checks the shared feed once a minute.

Observed block height

3,205,262

Latest tip reported by the provider.

Pending transactions

797

Snapshot count, not waiting time.

Confirmed transactions · 24h

155,815

Rolling count, including non-payment activity.

Mean block interval · 24h

2.26 min

637 reported blocks; 1440 ÷ count.

Estimated hashrate · 24h

3,049.88 TH/s

Provider work-rate estimate; not measured hardware.

Mining difficulty

95,864,124

Work threshold, not miner profitability.

Non-empty addresses

9,157,510

Addresses with balance, not people.

Mean confirmed fee · 24h

0.00005289 LTC

0.002943 USD at snapshot price

This total fee is not a litoshi/vB quote.

Explore the recorded history

Our archive stores provider snapshots every 15 minutes. It contains only collected observations, even when you request a longer lookback. All times below are UTC.

Loading collected observations…

Actual snapshot range
—
Collected snapshots
—
Populated time buckets
—
Selected measurement
—

The horizontal axis represents actual elapsed time. Lines join adjacent measured buckets only; longer gaps remain open. The vertical axis starts at zero. Partial edge buckets and buckets with fewer samples are marked separately.

Download raw snapshots · CSV
Bucket means and sample counts. A sparse bucket is still displayed; missing measurements are not zero.
Bucket start · UTCSelected meanValid metric samplesAll snapshotsBucket note
Loading observations…

Hourly means for 7/30 days; UTC daily means for 90/365 days. Means of rolling 24-hour fees and counts are neither period totals nor a transaction-weighted fee. The graph is a view of provider observations, not an independent node measurement. Collection method · Full research archive

Supply and subsidy arithmetic

Provider circulation estimate

77,780,948.64 LTC

92.60% of the 84,000,000 LTC cap

This estimate does not identify lost keys, coins offered for sale or an independently audited spendable supply. It shares the snapshot time and freshness label above.

Subsidy at observed height
6.25000000 LTC/block
Target daily issuance
3,600.00 LTC/day
Fixed-subsidy annualized rate
1.69%

Daily issuance assumes 576 blocks at the height-based subsidy and excludes transaction fees. The annualized rate holds that subsidy fixed for 365 days; it is not a forecast through a halving. Actual block production varies. Follow the next halving · Model merged-mining margins

Choose the evidence for your question

Is my payment stuck?

A pending transaction count cannot show what happened to your payment. Inspect its actual outputs, confirmation state and source time.

Check a transaction →

How long do confirmations take?

Our separate study follows sampled transactions first seen by one node. Read its coverage, eligibility rules and open outcomes alongside the reported times.

Inspect observed confirmation times →

Why did a mempool alert appear?

Two recorded count jumps show how a low preceding count can trigger an alert while a larger queue goes unflagged.

Read the frozen-data analysis →
What these measurements can and cannot tell you

Hashrate is an estimate

The snapshot uses Blockchair’s 24-hour estimate. It is inferred from work and block production, not a count of machines. Providers using different windows need not report the same estimate. Difficulty alone cannot measure mining profit.

Addresses and transactions are not users

One owner may control many addresses; one custodial address may represent many owners. Confirmed transactions include consolidations, self-transfers and other activity. These totals do not independently establish adoption, accumulation or payment volume.

Mean fees are not fee-rate recommendations

The provider reports average_transaction_fee_24h in litoshi; 100,000,000 litoshi equal 1 LTC. A rolling average total fee spans transactions of different sizes. Its USD equivalent uses the network snapshot’s price, which can differ from the header’s market feed. For a payment, use a fee rate and the signed virtual size in the fee calculator.

Source age and block age are separate

The snapshot is labelled current only when the source is no more than 15 minutes old, the observed tip timestamp no more than 30 minutes old, and refreshes have not failed. These conservative limits can mark a healthy network as cached during a long block gap. Fetching a cached response does not reset its source time.

Sources: Blockchair field definitions · Litecoin Core subsidy rules · Our network methodology

Additional series: daily means of provider fee estimates

Litecoinspace daily means of provider interval estimates, in USD per block, read from our cached history file. Each available interval has equal weight; the daily value is not weighted by its observed block count. This differs from the snapshot’s average fee per transaction and is not a live fee quote. USD uses the prices in those source observations.

Latest stored day: 2026-11-01 UTC. Cache file updated: 2026-11-01 02:00:02 UTC. The current UTC day is incomplete. Dates absent from the file stay absent.

Expand to inspect the daily table; JavaScript also draws the recorded series.

Estimate a payment fee
Available cached daily means. The UTC date, rather than the page load time, identifies the observation.
UTC dayMean interval fee estimate · USD/blockDay status
2026-08-010.5842Past UTC day · available provider intervals
2026-08-020.5021Past UTC day · available provider intervals
2026-08-030.5655Past UTC day · available provider intervals
2026-08-040.6407Past UTC day · available provider intervals
2026-08-050.6522Past UTC day · available provider intervals
2026-08-060.7529Past UTC day · available provider intervals
2026-08-070.8052Past UTC day · available provider intervals
2026-08-080.7034Past UTC day · available provider intervals
2026-08-090.7117Past UTC day · available provider intervals
2026-08-100.5947Past UTC day · available provider intervals
2026-08-110.5370Past UTC day · available provider intervals
2026-08-120.5579Past UTC day · available provider intervals
2026-08-130.7600Past UTC day · available provider intervals
2026-08-140.7072Past UTC day · available provider intervals
2026-08-150.6581Past UTC day · available provider intervals
2026-08-160.5801Past UTC day · available provider intervals
2026-08-170.7768Past UTC day · available provider intervals
2026-08-180.6766Past UTC day · available provider intervals
2026-08-190.6409Past UTC day · available provider intervals
2026-08-200.6906Past UTC day · available provider intervals
2026-08-210.8756Past UTC day · available provider intervals
2026-08-220.7327Past UTC day · available provider intervals
2026-08-230.6668Past UTC day · available provider intervals
2026-08-240.7502Past UTC day · available provider intervals
2026-08-250.6766Past UTC day · available provider intervals
2026-08-260.7047Past UTC day · available provider intervals
2026-08-270.7680Past UTC day · available provider intervals
2026-08-280.6754Past UTC day · available provider intervals
2026-08-290.6545Past UTC day · available provider intervals
2026-08-300.6771Past UTC day · available provider intervals
2026-08-310.6802Past UTC day · available provider intervals
2026-09-010.7934Past UTC day · available provider intervals
2026-09-020.6715Past UTC day · available provider intervals
2026-09-030.8129Past UTC day · available provider intervals
2026-09-040.7352Past UTC day · available provider intervals
2026-09-050.6708Past UTC day · available provider intervals
2026-09-060.6844Past UTC day · available provider intervals
2026-09-070.9434Past UTC day · available provider intervals
2026-09-080.7535Past UTC day · available provider intervals
2026-09-090.7096Past UTC day · available provider intervals
2026-09-100.8098Past UTC day · available provider intervals
2026-09-110.7848Past UTC day · available provider intervals
2026-09-120.6231Past UTC day · available provider intervals
2026-09-130.6637Past UTC day · available provider intervals
2026-09-140.7915Past UTC day · available provider intervals
2026-09-150.7920Past UTC day · available provider intervals
2026-09-160.7079Past UTC day · available provider intervals
2026-09-170.7026Past UTC day · available provider intervals
2026-09-180.7181Past UTC day · available provider intervals
2026-09-190.8589Past UTC day · available provider intervals
2026-09-200.7495Past UTC day · available provider intervals
2026-09-211.0010Past UTC day · available provider intervals
2026-09-220.7382Past UTC day · available provider intervals
2026-09-230.7751Past UTC day · available provider intervals
2026-09-241.2598Past UTC day · available provider intervals
2026-09-251.2485Past UTC day · available provider intervals
2026-09-260.9846Past UTC day · available provider intervals
2026-09-270.8935Past UTC day · available provider intervals
2026-09-281.0879Past UTC day · available provider intervals
2026-09-291.0240Past UTC day · available provider intervals
2026-09-300.9999Past UTC day · available provider intervals
2026-10-011.0561Past UTC day · available provider intervals
2026-10-020.9850Past UTC day · available provider intervals
2026-10-030.8580Past UTC day · available provider intervals
2026-10-040.9114Past UTC day · available provider intervals
2026-10-051.1207Past UTC day · available provider intervals
2026-10-061.0710Past UTC day · available provider intervals
2026-10-070.8771Past UTC day · available provider intervals
2026-10-080.9804Past UTC day · available provider intervals
2026-10-091.0905Past UTC day · available provider intervals
2026-10-100.8677Past UTC day · available provider intervals
2026-10-110.8601Past UTC day · available provider intervals
2026-10-120.9165Past UTC day · available provider intervals
2026-10-130.8581Past UTC day · available provider intervals
2026-10-140.7860Past UTC day · available provider intervals
2026-10-150.8093Past UTC day · available provider intervals
2026-10-160.7417Past UTC day · available provider intervals
2026-10-170.7793Past UTC day · available provider intervals
2026-10-180.7351Past UTC day · available provider intervals
2026-10-190.8196Past UTC day · available provider intervals
2026-10-200.8674Past UTC day · available provider intervals
2026-10-210.8544Past UTC day · available provider intervals
2026-10-220.8391Past UTC day · available provider intervals
2026-10-230.7641Past UTC day · available provider intervals
2026-10-240.7357Past UTC day · available provider intervals
2026-10-250.7023Past UTC day · available provider intervals
2026-10-260.6254Past UTC day · available provider intervals
2026-10-270.7321Past UTC day · available provider intervals
2026-10-280.6813Past UTC day · available provider intervals
2026-10-290.7800Past UTC day · available provider intervals
2026-10-300.7198Past UTC day · available provider intervals
2026-10-310.7127Past UTC day · available provider intervals
2026-11-010.4558Current UTC day · partial

Frequently asked questions

What does the address count measure?
It is the provider count of non-empty addresses, not active users or unique people. One person can control many addresses and one custodial address can represent many people.
Why can a value show cached or unavailable?
Cards retain the source timestamp. Snapshots older than 15 minutes or affected by a failed refresh are marked cached. Missing data is not replaced with an assumed healthy reading.
Does on-chain activity predict price?
No. Transactions can represent payments, self-transfers or consolidations. Hashrate, balances and transaction counts do not by themselves establish accumulation or predict a return.
Jarosław Wasiński
Editor-in-chief · Financial markets and Litecoin education

Editor-in-chief of Litecoin.watch and founder of MyBank.pl. His published work covers foreign exchange, financial education and Litecoin. On Litecoin.watch, his remit includes editorial direction, source transparency and the practical guides and research published by the site.

Background, selected work and editorial responsibility →

Founder of MyBank.plFinancial education and market analysisNamed editorial responsibility