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.
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.
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.
Measure
Observed amount
How to read it
Scheduled subsidy
900 LTC
144 × 6.25 LTC
All transaction fees
2.05386366 LTC
Sum of the 144 RPC fee totals
Available coinbase reward
902.05386366 LTC
Subsidy plus fees
Claimed coinbase outputs
902.05386366 LTC
Same total in this sample
Unclaimed allowance
0 LTC
Full allowance claimed in 144 of 144 blocks
Fee share of available reward
0.227687%
Fees ÷ (subsidy + fees), rounded
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.
Measure
Value
Interpretation
Total block fees
0.20157609 LTC
9.8145% of sample fees
Maximum entry fee
0.2 LTC
99.2181% of that block's fees
Fees from the other entries
0.00157609 LTC
Total minus the maximum
Base-chain entries
41
Coinbase and HogEx excluded
RPC median fee
427 litoshis
Includes HogEx among non-coinbase entries
Public MWEB kernel fees
0 LTC
No 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.
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.
Statistic
Litoshis
Denominator or boundary
Whole-sample base-chain mean
4,643.08
44,202 entries; MWEB/HogEx fees excluded
Mean after removing the 0.2 LTC entry
4,190.70
44,201 entries; sensitivity calculation
Largest block's base-chain mean
491,649
41 entries in that block
That block's other-entry mean
3,940.225
Its remaining 40 entries
Largest block's RPC median fee
427
42 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.
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.
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 situation
Check before acting
Useful next step
Sending from your own wallet
Current fee rate, virtual size, total fee and recipient amount
Pause 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
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.
Transaction Fee
In brief For ordinary transparent Litecoin transactions, the fee is total input value minus total output value, separate from a service withdrawal charge.
For an ordinary transparent Litecoin transaction, the network fee is the total input value minus all output values, including change. Wallets estimate it using transaction size and a fee rate, so sending more LTC does not automatically mean a higher fee. A service's withdrawal charge is a separate quote and may already cover network costs.
For example Fictional inputs total 1 LTC, while recipient and change outputs total 0.99999 LTC: the network fee is 0.00001 LTC.
Common mistake Confusing fee rate with total fee, leaving change out of output totals, or equating a service's withdrawal charge with the full network fee.
Compare: Network fee vs withdrawal fee
Transaction Fee
An ordinary transparent transaction's network fee is its total input value minus its total output value; transaction size and fee rate help determine the estimate.
Withdrawal Fee
A service sets its withdrawal charge under its own rules, and that charge can differ from the network fee on the transaction it broadcasts.
One example If a fictional service deducts a 0.001 LTC charge from a 1 LTC withdrawal, the recipient receives 0.999 LTC; these figures do not reveal the transaction's network fee.
Remember: Check the final account debit, recipient amount and minimum separately; add a network-fee estimate only if it is an additional charge, so the same cost is not counted twice.
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 An informal name for 0.00000001 LTC, the smallest Litecoin unit, with 100,000,000 in one LTC.
An informal name for the smallest Litecoin unit: 0.00000001 LTC. One LTC contains 100,000,000 litoshis. Some software uses the inherited label satoshi, so always check which coin and unit a screen means.
For example 10,000 litoshis equal 0.0001 LTC; 1 litoshi equals 0.00000001 LTC.
Common mistake Confusing a fee quoted per virtual byte with that many litoshis for the whole transaction.
In brief A peer-to-peer cryptocurrency with its own Scrypt proof-of-work network and a maximum issuance of 84 million LTC.
A peer-to-peer cryptocurrency launched in 2011. Litecoin uses Scrypt proof of work, targets an average 2.5-minute block interval and has an issuance schedule capped at 84 million LTC. Individual block times and payment acceptance times vary.
For example Sending 0.1 LTC on Litecoin transfers a fraction of one coin; you do not need to buy a whole LTC first.
Common mistake Assuming a token with LTC in its name on another network is automatically native Litecoin.
In brief The block-based wait before newly created mining-reward outputs can be spent, separate from ordinary pool payouts.
A rule that prevents freshly mined coinbase outputs from being spent until enough additional blocks have been built. A visible mining reward can therefore remain immature. An ordinary pool payout is a different transaction and should not be confused with the original coinbase.
For example A solo miner sees a new reward in the wallet but cannot yet select it to fund a payment.
Common mistake Applying mining-reward maturity to every incoming payment, or confusing a consensus spend height with a wallet's displayed confirmation policy.
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 Litecoin's optional layer that conceals amounts inside it, while base-chain and boundary activity can still reveal information.
Mimblewimble Extension Blocks, activated on Litecoin in May 2022. MWEB conceals amounts inside the extension layer; the base chain and boundary transfers can reveal information. Use maintained software and review the 2026 security postmortem.
For example An MWEB transfer uses compatible software and a different address format from an ordinary transparent Litecoin transfer.
Common mistake Assuming every LTC wallet or exchange accepts MWEB addresses, or that optional privacy removes all possible information leaks.
In brief A transaction identifier for looking up outputs and confirmations, which alone does not prove that a payment arrived.
The identifier used to look up a transaction. For an ordinary transparent Litecoin transaction it is shown as a 64-character hexadecimal string. Use it to inspect the transaction's outputs and confirmations; the ID alone does not prove a payment is confirmed.
For example Copy the TXID from your wallet's payment details into a Litecoin explorer to check the recipient output and confirmation count.
Common mistake Sharing a seed phrase to trace a payment, or treating a screenshot or TXID alone as proof that the expected amount arrived.
In brief Moving Litecoin from transparent mainchain addresses into private MWEB outputs (peg-in) and back out (peg-out).
Bridge operations connecting Litecoin's transparent base layer and optional Mimblewimble Extension Blocks (MWEB). A peg-in locks transparent coins and creates a confidential MWEB output, while a peg-out moves an MWEB balance back onto a standard L, M or ltc1 address.
For example Before depositing LTC to an exchange that only accepts ltc1q addresses, a user pegs out from MWEB into a transparent self-custody address first.
Common mistake Assuming peg-in or peg-out amounts remain hidden on-chain; only transfers strictly inside MWEB conceal values.
In brief A fee per unit of transaction size, rather than the total charge, with MWEB using additional accounting.
A fee per unit of transaction size, rather than the total charge. For ordinary transparent Litecoin, wallets commonly quote litoshis per virtual byte. The estimated total depends on both that rate and the transaction's virtual size; MWEB adds different accounting.
For example An illustrative 200-vB transaction at 2 litoshis/vB costs 400 litoshis, while a 400-vB transaction at that rate costs 800.
Common mistake Reading 2 litoshis/vB as a 2-litoshi total, or assuming a recommended rate guarantees a confirmation time.
In brief The size measure behind virtual bytes for ordinary transparent transactions; MWEB has additional accounting rules.
A measure of transaction size in weight units. For an ordinary transparent transaction, weight is three times its stripped size plus its total serialized size. BIP 141 virtual size divides weight by four and rounds up. Litecoin's MWEB-related transactions have additional accounting rules.
For example An ordinary transparent transaction weighing 561 weight units has a BIP 141 virtual size of 141 vB, not 561 vB.
Common mistake Using weight units as raw bytes or virtual bytes, or assuming a size calculation proves a transaction satisfies every relay rule.
In brief Searching for valid proof of work and proposing Litecoin blocks that other nodes independently check.
Searching for proof of work and assembling candidate blocks that follow a network's rules. Validating nodes independently check proposed blocks. An accepted Litecoin block can pay its miner the permitted subsidy and transaction fees; a pool participant is paid under the pool's scheme.
For example An ASIC connected to a pool contributes proof-of-work attempts; the pool pays according to its published scheme.
Common mistake Comparing coin revenue without subtracting electricity, pool charges, downtime and equipment costs.
In brief A block's position counted from zero in a chain, which does not uniquely identify the block or tell its time.
A block's position along a chain, starting with the genesis block at height zero. Height is an index, not a unique block identifier or a timestamp: competing blocks can occupy the same height on different branches. Use the block hash when identifying a particular block.
For example If a transaction remains in active-chain block 100 and the active tip is 102, it has three confirmations: blocks 100, 101 and 102.
Common mistake Treating height 100 as 100 confirmations, or assuming two nodes at the same height necessarily have the same chain tip.
In brief A fee-sizing unit for ordinary transparent transactions, usually weight divided by four and rounded up.
A size unit used when quoting fees for ordinary transparent transactions. The usual calculation divides transaction weight by four and rounds up; node policy can also account for signature-operation cost. It can differ from the raw serialized byte count. Use the size unit expected by the quoted fee rate.
For example A transparent transaction with weight 565 has a virtual size of 142 vB, because the division rounds up.
Common mistake Multiplying a litoshi-per-vB rate by an unrelated raw-byte count or assuming the same formula covers every MWEB component.
In brief Software or a device for managing wallet keys and payments, though a watch-only setup cannot sign on its own.
Software or a device that manages keys and helps you receive and send Litecoin. Coins are recorded on the blockchain. A watch-only wallet can show addresses and transactions without holding the keys needed to spend.
For example One wallet can generate several receiving addresses and still show them as a single combined balance.
Common mistake Thinking coins live inside the app, or that seeing a balance proves that the wallet can sign a spend.
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 rate of proof-of-work attempts; a network-wide figure is estimated and depends on the calculation method.
The rate of proof-of-work hash attempts, usually expressed per second. Network hash rate is estimated from blocks and difficulty rather than directly counted. Compare figures for the same algorithm; a higher rate alone does not establish decentralization or mining profitability.
For example One PH/s represents one quadrillion hash attempts per second; compare only figures for the relevant mining algorithm.
Common mistake Comparing Litecoin and Bitcoin hash-rate numbers as if Scrypt and SHA-256 work had identical costs.
In brief Deleting older block files after validation to save disk space, which can limit later rescans of old transactions.
A full node's deletion of older block files after validating them to reduce disk use. It still checks consensus rules and keeps current chain state, but the deleted history is unavailable for an ordinary local rescan. A pruning target is not a budget for the entire application.
For example A node can validate today's chain while lacking the old blocks needed to rescan a payment from years ago.
Common mistake Assuming pruning skips validation, or that switching it off instantly restores deleted historical block 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.
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.
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.