A short record of what changed, what was measured and one useful task to try. Reports link to their data and keep missing observations visible.
Node
In brief A participant running network software; a full node checks rules but need not keep all old block files.
A participant running network software. A full node independently validates rules; a pruned full node can discard older block files after validation. Not every node stores the complete historical blockchain.
For example A pruned full node checks the chain but later discards old block files to reduce disk use.
Common mistake Assuming every node is a miner, or that pruning means it skipped consensus validation.
In brief A group of transactions linked to the previous block under the network's rules.
A batch of transactions accepted under the network rules and linked to the previous block. Litecoin targets one new block every 2.5 minutes on average; a particular block may arrive sooner or much later.
For example Your payment may wait unconfirmed and then receive its first confirmation when a miner includes it in an accepted block.
Common mistake Treating the 2.5-minute target as a countdown or a maximum wait for your payment.
In brief One node's local collection of accepted but unconfirmed transactions, which may differ from other nodes' collections.
A node's local collection of unconfirmed transactions it currently accepts. Nodes can see, retain or remove different transactions, so there is no single global waiting room. Appearing in a mempool is not confirmation or a guarantee of later inclusion.
For example One explorer may see your unconfirmed transaction while another node has not received it or has already removed it.
Common mistake Assuming that absence from one mempool proves the payment was never broadcast or that a seen transaction must confirm.
In brief A transaction gains confirmations as blocks build on its inclusion, but those confirmations can fall if chain history changes.
A transaction receives its first confirmation when included in a block in the accepted chain. Each block then built on top adds another. A chain reorganization can reduce or remove the count. The recipient decides how many confirmations it requires. Litecoin targets an average 2.5-minute block interval; individual blocks can arrive sooner or much later.
For example A transaction in the latest accepted block has one confirmation; the next block raises that count to two.
Common mistake Confusing a wallet's sent message, a TXID or mempool visibility with the first confirmation.
In brief The share of a stated window or expected sample represented by usable records, which can still contain errors.
How much of a stated observation window or expected set is represented by usable records. The denominator may be scheduled polls, candle intervals or another declared sample. Coverage describes availability within that scope, not measurement accuracy or a complete view of the network.
For example If 90 of 96 expected price buckets are available, interval coverage is 93.75%; this says nothing about trades hidden inside those buckets.
Common mistake Reading missing observations as zero activity, or treating high coverage as proof that the sample is unbiased and error-free.
The median observed mempool count was 246 transactions. The archive contains 4,112 block headers for this period. 4,109 adjacent non-negative timestamp differences give a median of 103.0 seconds and a 90th percentile of 335.0 seconds.
Successful collection slots: 641/672 (95.4%). The longest gap between retrieved snapshots, including the week boundaries, was 435.0 minutes.
Mempool observations during this week. Hourly means of recorded snapshots. Line breaks mark missing hours.Counts of adjacent, non-negative block header timestamp differences. These are not measurements of payment confirmation time.Daily collection coverage and chart values
Missing heights: 21. Negative header-time differences excluded: 0. Overlapping fee snapshots and uneven sampling limit interpretation; this is not an independently measured network-wide average.
The median observed mempool count was 249 transactions. The archive contains 4,131 block headers for this period. 4,130 adjacent non-negative timestamp differences give a median of 100.0 seconds and a 90th percentile of 343.1 seconds.
Successful collection slots: 667/672 (99.3%). The longest gap between retrieved snapshots, including the week boundaries, was 30.0 minutes.
Mempool observations during this week. Hourly means of recorded snapshots. Line breaks mark missing hours.Counts of adjacent, non-negative block header timestamp differences. These are not measurements of payment confirmation time.Daily collection coverage and chart values
Missing heights: 0. Negative header-time differences excluded: 0. Overlapping fee snapshots and uneven sampling limit interpretation; this is not an independently measured network-wide average.
The median observed mempool count was 252 transactions. The archive contains 4,044 block headers for this period. 4,043 adjacent non-negative timestamp differences give a median of 105.0 seconds and a 90th percentile of 348.0 seconds.
Successful collection slots: 666/672 (99.1%). The longest gap between retrieved snapshots, including the week boundaries, was 30.0 minutes.
Mempool observations during this week. Hourly means of recorded snapshots. Line breaks mark missing hours.Counts of adjacent, non-negative block header timestamp differences. These are not measurements of payment confirmation time.Daily collection coverage and chart values
Missing heights: 0. Negative header-time differences excluded: 0. Overlapping fee snapshots and uneven sampling limit interpretation; this is not an independently measured network-wide average.
The median observed mempool count was 263 transactions. The archive contains 3,757 block headers for this period. 3,756 adjacent non-negative timestamp differences give a median of 111.0 seconds and a 90th percentile of 370.0 seconds.
Successful collection slots: 670/672 (99.7%). The longest gap between retrieved snapshots, including the week boundaries, was 15.0 minutes.
Mempool observations during this week. Hourly means of recorded snapshots. Line breaks mark missing hours.Counts of adjacent, non-negative block header timestamp differences. These are not measurements of payment confirmation time.Daily collection coverage and chart values
Missing heights: 0. Negative header-time differences excluded: 0. Overlapping fee snapshots and uneven sampling limit interpretation; this is not an independently measured network-wide average.
The median observed mempool count was 257 transactions. The archive contains 4,180 block headers for this period. 4,179 adjacent non-negative timestamp differences give a median of 102.0 seconds and a 90th percentile of 337.0 seconds.
Successful collection slots: 669/672 (99.6%). The longest gap between retrieved snapshots, including the week boundaries, was 15.0 minutes.
Mempool observations during this week. Hourly means of recorded snapshots. Line breaks mark missing hours.Counts of adjacent, non-negative block header timestamp differences. These are not measurements of payment confirmation time.Daily collection coverage and chart values
Missing heights: 0. Negative header-time differences excluded: 0. Overlapping fee snapshots and uneven sampling limit interpretation; this is not an independently measured network-wide average.
We now retain source-stamped network snapshots and recent block headers. The first completed weekly report will appear after a full UTC week has observations on all seven days and at least 90% of its collection slots succeed. Until then, the research page shows exactly the sample collected so far. Each completed report will include two SVG charts, daily coverage, frozen CSV inputs and a reproduction script.
Current partial week: 640 snapshots on 7 UTC days. This is not a full-week comparison.
Release to know about
Our Core update page explains the maintainer notice for 0.21.5.8 and links to the original release and download-verification guide.
One useful task
Take a completed public transaction from your own wallet and use the transaction checker. Compare the network's confirmation count with the receiving service's policy. The two describe different stages of a payment.
What subscribing means
The RSS feed contains this launch note and newly completed statistical reports. It does not subscribe you to email, require an account or create a daily price prediction. Reports are generated from the archive using a published method.