There is direct evidence of Litecoin payments at CoinGate. Its reports put LTC’s payment share at 13.1% in 2024, 14.4% in 2025 and 18.0% in the first half of 2026. These are one provider’s reported shares, not Litecoin’s share of all retail spending or a count of unique users.
The more revealing finding is in the denominator. The 2025 report lists 1,424,519 completed orders, including 100,114 off-chain transactions that it excludes from crypto-specific analysis. Multiplying 14.4% by every order produces about 205,131. Applying that share to the remaining base produces about 190,714. The gap is about 14,416 estimated orders.
We publish both calculations so that a reader can see how an apparently simple adoption statistic changes. Neither is an exact reconstructed LTC ledger: the provider publishes a rounded percentage, and we have not obtained its underlying merchant records.
Three periods, with scope kept visible
| Period | LTC payment share | All-provider order total | Scope caution | Source |
|---|---|---|---|---|
| 2024 full year | 13.1% | 1,677,288 | Do not assume the 2025 off-chain exclusion applies identically | 2024 report |
| 2025 full year | 14.4% | 1,424,519 | 100,114 off-chain orders excluded from crypto-specific analyses | 2025 report |
| H1 2026 | 18.0% | 782,403 | Six months; not a full-year count | H1 2026 report |
Our denominator check
Using the 2025 report’s stated exclusion, the remaining base is 1,424,519 − 100,114 = 1,324,405. If the reported LTC share uses that crypto-specific base, the central rounded-share estimate is 1,324,405 × 0.144 = 190,714.32. Including the excluded rows instead adds 100,114 × 0.144 = 14,416.416.
If 14.4% was rounded to the nearest 0.1 percentage point, the underlying share could differ by up to 0.05 percentage points before tie handling. On the excluded base, that alone moves the estimated count by about 662.2 orders in either direction. This is a rounding sensitivity, not a confidence interval or a guarantee that the denominator is correct.
We therefore do not advertise 190,714 as an exact observed count, or calculate a precise year-on-year LTC count change using inconsistent bases. A provider clarification or exact asset-level counts would improve this comparison. The annual share rose by 1.3 percentage points; that fact alone cannot establish whether the absolute number of LTC orders rose.
Order count, payment value and settlement currency differ
One €5 order and one €5,000 order each contribute one to an order count. A payment share by count cannot be treated as a share of sales value. Repeated orders by one buyer also do not count unique people.
The coin a customer pays and the asset a merchant finally receives are another distinction. A checkout can accept LTC while the merchant settles into fiat. Evidence of that checkout option is evidence of payment use, not proof that the merchant chose to hold Litecoin as a treasury asset.
What blockchain counts cannot fill in
An ordinary transaction may batch many recipients or move funds within one organisation. HogEx can carry a large protocol balance. MWEB does not reveal private amounts and owners. Our 50-block classification study illustrates why output totals and transaction counts should not be converted into retail sales statistics.
Combining two payment processors’ shares is also invalid without their raw counts and comparable scope. Their merchant mixes, regions, invoice rules and support for off-chain routes can differ. We removed the previous page’s unsourced cross-provider rankings and global adoption claims.
If you are deciding whether to accept LTC
Measure your own checkout funnel: invoices created, funded before expiry, funded late, underpaid, refunded and settled into your accounting currency. Keep payment count and value separate. Those figures answer a merchant’s question more directly than a global popularity slogan.
Use the payment workflow and the underpayment and refund guide to define those outcomes. A merchant pilot can then compare actual processing and reconciliation effort against its existing methods.
Reproduce the arithmetic
Declared inputs and standard-library Python code are public. Save both with input-sha256.json into one folder and run python analyze.py.txt .. Compare with results.json.
These files reproduce declared arithmetic. They do not verify hardware availability, execute purchases or audit a company’s holdings.
Sources and review scope
Reviewed against the linked materials on 2 October 2026. Calculations and drafting were AI-assisted; no independent external review or personal attendance is claimed. Original publication date retained. See our corrections policy.
