Litecoin Latest Blocks

The newest blocks as miners find them — one every ~2.5 minutes on average, each carrying the 6.25 LTC subsidy plus fees.
-- loading…
Last 15 Blocks
HeightAgeIntervalTxnsFees (LTC)Size (MB)Pool
loading blocks…
Interval = time since the previous block. Fees = total transaction fees paid to that block's miner (on top of the 6.25 LTC subsidy). Ages and intervals use miner-reported timestamps — an occasional negative interval is clock skew, not a chain problem. Heights link to the full block on litecoinspace.org.
Avg interval (last 10)
--
vs 2m 30s target
Avg fees / block
--
LTC per block, last 15
Avg txns / block
--
transactions, last 15
Avg block size
--
MB serialized, last 15

What is a block?

A block is a batch of transactions bundled under a small header that commits to the previous block's hash, a merkle root of the transactions, a timestamp and a nonce. Miners race to find a header hash (scrypt, in Litecoin's case) below the current difficulty target; the winner appends the block to the chain and collects the 6.25 LTC subsidy plus every fee in the block. Because most Litecoin pools merge-mine Dogecoin via AuxPoW, the same winning work usually also produces a DOGE block candidate at no extra energy cost.

Why block intervals are random

Hashing is memoryless: every hash attempt is an independent lottery ticket, and past effort builds no progress toward the next block. Block arrivals therefore form a Poisson process, and the gaps between them follow an exponential distribution — the expected interval is 2.5 minutes, but the actual intervals in the table scatter from a few seconds to ten minutes and beyond. That spread is the system working as designed.

P(no block for t minutes) = e^(−t / 2.5)
P(gap ≥ 15 min) = e^(−6) ≈ 0.25% of gaps → still ~1–2 per day at 576 blocks/day
average blocks per day = 86,400 s ÷ 150 s target = 576

From block pace to the difficulty adjustment

Individual intervals are noise, but their average over 2,016 blocks (~3.5 days on Litecoin) is the signal the network retargets on. If the epoch's blocks averaged faster than 2.5 minutes, difficulty rises proportionally at the next retarget; slower, and it falls. The "avg interval" tile above is a small live sample of that same pace.

new_difficulty = old_difficulty × (5,040 min ÷ actual_time_of_last_2,016_blocks)
2,016 blocks × 150 s target = 5,040 minutes = 3.5 days per epoch

Why it matters for miners

The Fees column is the variable half of your revenue: hashprice is built from the subsidy plus the average fees per block, so the fee level here feeds earnings per MH/s directly — though on Litecoin fees are usually a small fraction of the 6.25 LTC subsidy, and merged-mined DOGE rewards often matter more. Block pace is your early warning for the next retarget, which on Litecoin lands roughly twice a week rather than fortnightly. Interval variance is also why small pools see lumpy payouts even with healthy hardware.

Mining LTC without merge-mining DOGE leaves revenue on the table — the same scrypt work counts on both chains. The calculator shows the combined picture.

FAQ

Why did a Litecoin block just take 15 minutes?
Block discovery is a Poisson process: every hash is an independent lottery ticket, so the gaps between blocks follow an exponential distribution around the 2.5-minute average. About 0.25% of gaps run longer than 15 minutes — with 576 blocks a day that is still roughly one or two per day — and they are normal variance, not a network problem.
How many Litecoin blocks are mined per day?
576 on average — 86,400 seconds per day divided by the 150-second block target. The actual daily count wanders with luck, and runs slightly above 576 while hashrate is growing inside a difficulty epoch.
What decides how big a Litecoin block can be?
Litecoin uses a 1 MB base block size with SegWit's 4x weight allowance — the same structure as Bitcoin. Typical Litecoin blocks sit far below the limit, which is why fees stay low even at the 2.5-minute pace.
Source: litecoinspace.org API (blocks, fees, pool tags) — BasinTwo's own Litecoin full node is synced and cross-checks this feed live. Updated every 60s in your browser.