Analysis

One 0.2 LTC fee changed the picture in our 144-block sample

One transaction supplied 9.74% of all fees in our 144-block sample. Its block still had a median fee of just 427 litoshis. See what each figure measures before choosing a fee for your own payment.

A pencil-drawn scale contrasts several small disks with a single exceptional disk.

Editorial illustration of an outlier; it is not a plot of the observed fee distribution.

On this page

Dotted-underlined terms open a quick definition. Close it to keep reading.

One of 0.2 LTC accounted for 9.74% of all fees in the 144 we examined. In its block, the RPC median fee was just 427 , or 0.00000427 LTC. Both figures are correct. They answer different questions.

Our read-only Core capture found 2.05386366 LTC in fees beside 900 LTC of scheduled subsidy. We reconciled those amounts with the actual , separated the public MWEB kernel fees and tested how much that single large fee affected the average. The result gives beginners a practical way to read fee statistics without copying an outlier into their next payment.

Observation date: captured on 3 October 2026, 23:12:19–23:12:47 UTC; release date 4 October in Europe/Warsaw. This is a frozen network observation, not a live recommendation.

What we measured, and which period it covers

The fee sample contains every block from height 3,188,896 through 3,189,039, inclusive. We used one synced, pruned Litecoin Core 0.21.5.8 . The final height and hash form the study boundary; we rechecked the captured heights against the active chain after collection.

The first and last block headers carry times of 17:47:08 and 23:09:17 UTC on 3 October. Their difference is 5 hours, 22 minutes and 9 seconds. Those are miner-declared header times. They are not when our node first saw the blocks, nor a record of how long any customer waited.

There are no missing heights inside this range. That makes the totals reproducible for the selected sample. It does not make a little over five hours representative of a day, month or future subsidy era. A 144-block window is approximately six hours at the 150-second target interval; actual production varies.

The underlying block observations and one-row-per-block CSV let you change the reporting window or check an individual result.

Fees supplied 0.228% of the available LTC reward

For each block, we added the protocol subsidy to the RPC fee total and compared that allowance with the sum of its coinbase outputs. All 144 sampled blocks claimed the full allowance. The fees were transferred from transaction inputs; the subsidy was the newly issuable amount.

Observed LTC reward accounting for blocks 3,188,896–3,189,039. MWEB fees are included in the fee total.
MeasureObserved amountHow to read it
Scheduled subsidy900 LTC144 × 6.25 LTC
All transaction fees2.05386366 LTCSum of the 144 RPC fee totals
Available coinbase reward902.05386366 LTCSubsidy plus fees
Claimed coinbase outputs902.05386366 LTCSame total in this sample
Unclaimed allowance0 LTCFull allowance claimed in 144 of 144 blocks
Fee share of available reward0.227687%Fees ÷ (subsidy + fees), rounded
900 LTC subsidy and 2.05386366 LTC fees supplied the available reward.
Frozen 144-block reward accounting. The second bar uses a fee-only scale; MWEB is already included. On narrow screens, scroll the chart. Open full-size SVG.

Equality is an observation here, not a rule requiring miners to take everything. Core rejects a coinbase that pays more than the allowed reward; paying less is possible. Keeping claimed and available amounts separate avoids turning that upper limit into an assumed issuance total.

The highest-fee block was dominated by one entry

Block 3,189,026 contained 0.20157609 LTC in fees. Its maximum non-coinbase entry fee was exactly 0.2 LTC. There were no kernel fees in that block. Since the entire fee total was below 0.4 LTC, two entries could not both have paid 0.2 LTC. This establishes one maximum-fee entry without needing to identify its sender.

Accounting inside block 3,189,026. One LTC equals 100,000,000 litoshis.
MeasureValueInterpretation
Total block fees0.20157609 LTC9.8145% of sample fees
Maximum entry fee0.2 LTC99.2181% of that block's fees
Fees from the other entries0.00157609 LTCTotal minus the maximum
Base-chain entries41Coinbase and HogEx excluded
RPC median fee427 litoshisIncludes HogEx among non-coinbase entries
Public MWEB kernel fees0 LTCNo MWEB fee contribution in this block

We did not reconstruct the , its owner, purpose or software settings. A large fee does not by itself establish a mistake, a special commercial payment or network congestion. Those explanations would require additional evidence.

The concentration also matters at block level: the ten highest-fee blocks, out of 144, supplied 35.4463% of all sampled fees. The largest block was 14.13 times the mean block total and 21.34 times the median block total. Treating that block as “typical” would substantially exaggerate the fees in this window.

The ten highest-fee blocks contributed 35.4463 percent of fees in 144 blocks.
Ranked block totals, not time or payer identity. Bars start at zero. On narrow screens, scroll the chart. Open full-size SVG.

Why “the average Litecoin fee” needs a denominator

We counted 44,490 base-chain entries reported by the RPC. That included 144 coinbases and 144 HogEx transactions. Removing both leaves 44,202 base-chain transactions. This count can include and other activity; it is not a count of unique users or purchases. Separately, the extension blocks contained 50 public MWEB kernels.

Our base-chain mean divides fees excluding HogEx by entries excluding coinbase and HogEx. The calculation is 2.0523329 LTC ÷ 44,202, giving approximately 4,643.08 litoshis per entry. We add numerators and denominators across blocks before dividing; averaging the individual block averages would give small and large blocks equal influence.

How the same observations produce different fee statistics. Sensitivity rows remove one entry mathematically; they do not describe a different observed chain.
StatisticLitoshisDenominator or boundary
Whole-sample base-chain mean4,643.0844,202 entries; MWEB/HogEx fees excluded
Mean after removing the 0.2 LTC entry4,190.7044,201 entries; sensitivity calculation
Largest block's base-chain mean491,64941 entries in that block
That block's other-entry mean3,940.225Its remaining 40 entries
Largest block's RPC median fee42742 non-coinbase entries, including HogEx

Removing the single entry lowers the whole-sample base-chain mean by 9.743%. This is a sensitivity check: an outlier influenced the summary. It is not a recommendation to delete inconvenient observations. The full total remains the correct accounting of what those blocks contained.

Removing one 0.2 LTC entry changes the sample and block means by different amounts.
Observed totals and explicitly labeled leave-one-entry-out sensitivities; litoshis per entry, not per virtual byte. On narrow screens, scroll the chart. Open full-size SVG.

The RPC implementation includes HogEx in its non-coinbase fee statistics. Its percentiles are weighted by , rather than one equal vote per transaction. Rates use integer units. A median of block medians cannot recover the global transaction median. We therefore report neither that shortcut nor a claimed global “typical customer fee.”

MWEB fees are part of the total, not an extra reward

The public MWEB kernels contained 0.00153076 LTC in fees, or 0.07453% of the sample's entire fee total. These are fee fields; they do not reveal the confidential transaction amounts or owners.

HogEx is the base-chain transaction connecting the extension block to the preceding state and peg-ins and peg-outs. The MWEB accounting check requires its fee to equal the extension block's total fee. The RPC already counts that HogEx fee.

Our reconciliation is therefore 2.0523329 LTC of base-chain fees + 0.00153076 LTC of MWEB fees = 2.05386366 LTC. Adding the kernel total to the RPC total would double-count it. Public kernel counts also cannot simply be appended to the base-chain count and labelled “payments.”

The companion hashrate-window analysis uses the same final block and shows why a reward table and a network rate are separate measurements.

What this says about mining, and what it does not

For this selected period, Litecoin coinbase allowances were overwhelmingly subsidy-funded. That is a measured composition of LTC rewards. It is not a calculation of an operator's profit or the spending needed to attack the network.

We did not collect Dogecoin rewards, pool payouts, electricity bills, hardware costs, market prices or other merged- income. An operator may earn revenue on another chain; that revenue does not become a Litecoin transaction fee. Converting this table into dollars would need a stated price and timestamp, while calculating profit would require costs and the operator's actual share of rewards.

Our earlier subsidy revenue model shows why assumptions matter. This study supplies a short observed fee window alongside that model. Neither supports a prediction that present fees will fund a particular future level of mining. The guide to the eventual zero-subsidy boundary separates calculable from uncertain long-range economics.

How to choose a fee for your next payment

Do not enter 0.2 LTC or the sample's mean fee just because it appears in this article. A historical included fee describes one transaction's construction and circumstances. Your transaction can use a different number of inputs, outputs and , under different current conditions.

A beginner's fee decision workflow. The study's frozen figures are not current quotes.
Your situationCheck before actingUseful next step
Sending from your own walletCurrent fee rate, virtual size, total fee and recipient amountUse the wallet preview and our fee calculator
Withdrawing from an exchangeThe service's withdrawal charge, chosen network and net amount receivedRead the exchange confirmation screen; its charge need not match the transaction fee
Payment waiting for confirmationTransaction ID, confirmation status and whether it is visibleStart with the transaction checker
Fee looks unusually largeTotal fee versus fee rate, input count and unitsPause before signing and inspect the transaction preview

First separate a total from a rate: LTC per transaction is not litoshis per virtual byte. Then inspect how many inputs the consumes. Finally compare the quoted rate with a current recommendation whose source time is visible. The calculator's editable example and this article's observed average are not substitutes for that check.

Once broadcast, a payment's timing also depends on block production and other conditions. An expensive fee alone is not a delivery guarantee. Our node confirmation study explains the difference between local observations, successful and transactions still waiting.

Reproduce the results or inspect a different block

Download the research package and verify it against SHA256SUMS.txt. The README documents the schema and commands. Results JSON retains more precision than the rounded tables.

The public offline analyzer recomputes totals from the frozen files. Across the joint fee and package, it passed 2,223 assertions covering input hashes, chain continuity, accounting bounds and reconstructed calculations. Those checks help catch inconsistent data or arithmetic; they are not an independent review or proof that this sample represents other periods.

The separate capture script documents the read-only RPC collection. Replaying the offline package does not require a wallet, an account or sending any funds. A fresh capture requires your own appropriate Core node and produces different observations. Keep the original files when making comparisons. For everyday use, download the fee-reading checklist.

Sources, review record and limits

Primary code references were checked against the pinned Litecoin Core v0.21.5.8 source: block statistics, reward validation and MWEB accounting. No transaction owner, motive or economic payment volume was inferred.

This is original analysis of one read-only capture from one . Header times are not receipt times. The dataset is fixed at its recorded boundary, can be checked against another node and does not update with this page. AI assisted the drafting and analysis workflow; the public code, observations and checks support the stated calculations. No separate independent reviewer is recorded. The responsible editor is identified in the byline. Corrections should identify the block, field or calculation so they can be reproduced.

Method and data

Downloadable data or code · Observed data / replay.

Content review recorded: 2026-10-04. The review record does not identify a separate independent reviewer. An edited date above records an edit, not a new fact-check. AI-assisted editing or new artwork alone does not complete a source review.

Next scheduled review: 2027-01-02.

Sources saved with the review:

Research records

  • Observed data / replay · Core 0.21.5.8 · frozen network snapshot 2026-10-04-v1

    144 fixed mainnet blocks, subsidy/fees/coinbase reconciliation and MWEB decomposition. Header-time window; no payer identity, live quote, DOGE income or mining-profit audit.

    One 0.2 LTC entry supplied 9.74% of fees; removing it lowered the base-chain sample mean from 4643.08 to 4190.70 litoshis.

    Method & reproduction · Download data / results · Versioned citation

Report dates identify the evidence cutoff or release. Recalculating an export checks its arithmetic; a model is not an observed outcome.

See the article body for source links and any downloadable materials. Editorial method · Corrections · Report an issue

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.pl Financial education and market analysis Named editorial responsibility