Litecoin.watch · Research & practical tools
Observed Litecoin confirmation times
A rolling study from our own Litecoin Core node: first mempool observation, first observed block inclusion, and every incomplete outcome.
Node synchronizing
The node is validating the Litecoin blockchain. No eligible timing measurements are collected during initial synchronization. The first results will appear here after it catches up and observes new transactions.
- Latest collector update
- 27 Sep 2026, 00:44 UTC
- Validated height / known headers
- 2,099,366 / 3,184,977
- Core version
- /LitecoinCore:0.21.5.8/
- Connected peers
- 10
This page is a snapshot; reload to get a new update. Initial synchronization can take hours or days. A node's header count is its current view, not independent proof of the network's highest height.
Every sampled outcome counts
Rolling seven-day cohort, selected by first observation time. A transaction qualifies when the first eight hexadecimal characters of its txid, interpreted as an integer, are divisible by 16. This fixed rule selects roughly one in sixteen eligible txids.
No eligible sample has been collected yet. There is no simulated confirmation-time chart.
| Outcome | Transactions | Meaning |
|---|---|---|
| Observed in a block | 0 | An eligible mempool observation was matched to the next observed block. |
| Still in the mempool | 0 | No block inclusion has been observed yet. The waiting time remains open. |
| Left the mempool without a matched block | 0 | Could be eviction, replacement, a conflict or a missed inclusion. The cause is not inferred. |
| Interrupted by a collection gap | 0 | Continuity was lost before an eligible confirmation observation. |
| Block membership awaiting recheck | 0 | Prior results are withheld while their confirming blocks are checked after an interruption or chain change. |
| Confirming block no longer canonical | 0 | The original observed confirmation is excluded from timing summaries. |
| Total sampled transactions | 0 | Unconfirmed and interrupted outcomes remain in the denominator. |
The CSV refreshes about once a minute and may lag this table. UTC timestamps are Unix seconds. It retains original observed inclusion details even when a record is later excluded; use the state column when analysing it.
Time to the first observed block inclusion
This distribution includes only 0 currently matched confirmations. It excludes pending and interrupted outcomes listed above, so it cannot estimate how long every payment will take. Very fast transactions that enter a block between polls may never enter the cohort.
The chart will appear after the observer records an eligible confirmation.
Median and 90th percentile are withheld until at least 20 eligible confirmations are available. That threshold does not establish statistical representativeness.
Collection coverage
Only consecutive valid snapshots at most 30 seconds apart contribute observed time. Syncing, disconnected periods, restarts, inconsistent reads and jumps over more than one block create gaps. The table includes the current partial UTC day; the oldest day can also be partial at the rolling window boundary.
| UTC date | Recorded polls | Covered hours | Excluded baseline entries |
|---|---|---|---|
| 2026-09-26 | 341 | 0.00 | 0 |
| 2026-09-27 | 179 | 0.00 | 0 |
Baseline exclusions count mempool entries at each new baseline, not unique transactions. A full day has 24 hours. Intervals are assigned to the day in which their ending poll occurs, with up to 30 seconds of boundary imprecision.
How to read this study
Our private, pruned mainnet node has no wallet. Polling measures when this observer detects a transaction and a block, not when a sender broadcast it or a miner found the block. Each endpoint can lag its event by a polling interval; relay delays and the node's mempool policy also affect the sample. This is one observer, with no guarantee that another node sees the same mempool.
Only transactions exposed by Core's public mempool and block transaction lists are eligible. Private MWEB transfers are not measured individually. Reappearing sampled txids keep their first record within the window; a lost observation is not restarted as a shorter wait. No conclusions about fee recommendations, exchange crediting, attack probability or network-wide payment speed follow from this chart alone.