AI-generated editorial illustration of a Litecoin coin, a blank receipt and a caliper measuring an abstract transaction strip.
On this page
Dotted-underlined terms open a quick definition. Close it to keep reading.
A fee quote is useful only when you know what it measures. The transaction's , an and the cost of converting money into LTC can be three different amounts. A small network fee does not establish that the complete payment route is the cheapest.
Expanded review · 22 October 2026. This guide covers ordinary transparent transactions. Signed-size observations below come from our archived Core 0.21.5.8 regtest study; other numbers are explicitly hypothetical. No new mainnet payments or live fee measurements were made for this update.
The basic units
One LTC equals 100,000,000 . A in litoshis per , abbreviated litoshi/vB, describes a price for transaction size. A total fee in LTC describes what the whole transaction pays. Neither is a percentage of the amount sent.
Total fee in litoshis = virtual size × rate in litoshi/vB
Total fee in LTC = total litoshis ÷ 100,000,000
For a hypothetical 200 vB transaction at 2 litoshi/vB, the fee is 400 litoshis, or 0.00000400 LTC. Sending a larger LTC amount need not increase the fee if the input and output structure stays the same. Selecting additional inputs can increase it even when the recipient receives less.
For conventional transactions, virtual size is the transaction's weight divided by four, rounded up. Raw serialized bytes and virtual bytes are different quantities. The BIP 141 size definitions explain the witness discount. Our simple multiplication examples use whole-number rates and sizes; actual also apply integer rounding and their own construction rules.
Hypothetical rate: 2 litoshis/vB. One LTC equals 100,000,000 litoshis. Values and explanations are also provided in the text.
Why two payments can cost different amounts
A wallet spends whole unspent outputs. Several small receipts may require several inputs, while one sufficiently large receipt may fund the same payment with one input. A returns the remainder to the sender. It contributes to size but is not a service charge. See the worked UTXO and coin-control guide for value conservation and privacy consequences.
Recorded signed candidates from the September 2026 isolated study: P2WPKH inputs, recipients and change; experimental rate 10 litoshi/vB.
Construction
Recorded virtual size
Recorded total fee
1 input, 1 recipient, 1 change
141 vB
1,410 litoshis / 0.00001410 LTC
2 inputs, 1 recipient, 1 change
208 vB
2,080 litoshis / 0.00002080 LTC
5 inputs, 5 recipients, 1 change
536 vB
5,360 litoshis / 0.00005360 LTC
10 inputs, 5 recipients, 1 change
874 vB
8,740 litoshis / 0.00008740 LTC
These are particular signed transactions, not permanent sizes for all wallets. Signatures and script types can change the result. The study checked candidates locally without broadcasting or them; its setup funding cost is excluded. The original JSON preserves signed hex, size and policy results. The batching study explains its 12 alternative comparisons and assumptions.
For five recipients with matched total input counts, the recorded batch used 536 vB instead of 705 vB for five separate one-input payments: 169 vB, about 23.97%, less. A pre-consolidated one-input batch used 265 vB, but that comparison excludes any earlier consolidation cost. Do not present the larger saving as available to every fragmented wallet.
Convert a Core estimate without changing its meaning
In Core 0.21.5.8, estimatesmartfee returns a rate in LTC per 1,000 virtual bytes. Check your own version's help before using any RPC field: similar names in other wallets can have different units. These commands inspect information; they do not send a payment:
litecoin-cli help estimatesmartfee
litecoin-cli estimatesmartfee 6 "CONSERVATIVE"
litecoin-cli getmempoolinfo
Suppose an estimator returned {"feerate":0.00002000,"blocks":6}. This is a fabricated response for arithmetic, not a current quote. Convert it as follows:
Multiplying an LTC/kB value directly by a vbyte count overstates the fee by 1,000. Treating LTC/kB as LTC/vB is the same error. Conversely, dividing twice understates the intended rate. Keep the original unit alongside every copied number. The versioned RPC implementation defines the result and its insufficient-data response.
Estimation is not a confirmation guarantee
A target of six expresses the estimator's objective, not a reservation in an upcoming block. Read the returned target and mode, and inspect any error. An insufficient-data response means that this cannot supply that estimate; it does not mean a zero fee is appropriate.
Use the wallet's final preview for the transaction being authorized. An unsigned approximation can change after selection, change creation and signing. If an invoice requires exactly 1 LTC, verify whether the wallet adds the fee to your debit or subtracts it from the amount delivered. A hypothetical 1,410-litoshi fee means either a 1.00001410 LTC debit for a 1 LTC recipient payment, or a 0.99998590 LTC recipient payment if the total debit is fixed at 1 LTC.
Mempools and relay policy
Each node has a local and policy settings. A transaction visible to one node is not proof of universal propagation or future inclusion. Inspect the fee tracker as dated context and the mempool guide for local minimums, rejection and observation limits.
is a separate output-policy calculation. For ordinary P2PKH, P2SH and P2WPKH outputs, the pinned Core defaults yield thresholds of 5,460, 5,400 and 2,940 litoshis respectively. These follow the dust calculation and the 30,000-litoshi/kB value in policy constants. They are configurable policy values, not a network-wide minimum payment promise.
Increasing the transaction's total fee does not repair an output that remains below a node's dust threshold. The controlled boundary study separates that test from transaction fee rate. Also keep MWEB separate: Core's fee-rate implementation includes an weight component which the ordinary transparent formula here omits.
What to do about a delayed payment
Diagnose the payment state before spending more money.
Observed state
Useful next check
What an extra fee cannot fix
Provider says pending, no transaction ID
Withdrawal queue and provider support
A transfer the provider has not broadcast
Unconfirmed transaction ID
Wallet status, inputs, rate and local acceptance
Automatic universal relay
Confirmed, service has not credited
Required confirmations, deposit route and service records
Internal account crediting
Wrong route or destination
Actual chain, output and receiver's recovery policy
Changing an already confirmed destination
requires a valid replacement and suitable wallet and node support. requires a spendable output and a child transaction whose package can satisfy relevant policy. Neither is a generic “speed up” button for every wallet. Follow the cancellation and replacement guide or the pending-payment diagnosis before trying another transfer. Sending a new independent payment can pay the recipient twice.
Reduce avoidable cost without hiding trade-offs
Batching shares overhead and change, but can associate recipients publicly and complicate accounting. Consolidation pays a fee now and combines receipt histories; compare the complete consolidation-plus-future-payment path with waiting. It may cost more if those inputs would otherwise be spent separately. An -format change helps only through the scripts actually spent and created, with support at both ends.
A withdrawal may be one output in a much larger batch. Its fixed withdrawal charge need not equal that transaction's network fee or a uniquely attributable share of it. Record the provider's quote and the wallet receipt separately. For frequent payouts, compare minimum withdrawals and future input count as well as the immediate fee.
Compare other payment routes honestly
Write down the complete route: acquisition, spread, transfer, recipient conversion and withdrawal. Use one currency and one observation time for comparisons. A route advertising no network charge can still include conversion costs; a small fee can be immaterial beside a large spread. requirements and supported destinations also affect whether the route solves the payment.
Download the measured-size and hypothetical-rate cases and quote checklist. The CSV labels the original measured rows separately from conversions. It does not predict congestion or allocate an exchange's batch fee to individual customers.
Frequently asked questions
Does sending more LTC always cost more?
No. Input count, scripts, outputs and fee rate determine the ordinary transaction fee. The transferred value alone does not determine virtual size.
Is LTC/kB the same as litoshi/vB?
No. Multiply an LTC/kB rate by 100,000 to obtain litoshi/vB. For example, 0.00002000 LTC/kB equals 2 litoshi/vB.
Is the study's 10 litoshi/vB a recommendation?
No. It was a fixed experimental rate for signed candidates in isolated regtest. Check your wallet and current dated network context.
Does a missing estimate mean zero fee?
No. Core can return an insufficient-data error. That describes the estimator's evidence, not a free confirmation opportunity.
Can I fix a dust output by raising the fee?
Not if the output remains below the applicable dust threshold. Dust policy and total transaction fee are separate checks.
Is an exchange withdrawal fee paid entirely to miners?
Not necessarily. It is the provider's charge. Its network transaction can batch many withdrawals and pay a different total fee.
Litecoin (LTC)
A peer-to-peer cryptocurrency created by Charlie Lee in 2011 as a lighter, faster alternative to Bitcoin. It uses the Scrypt hashing algorithm, has 2.5-minute block times, and a maximum supply of 84 million coins.
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.
The LTC left for the miner when a transaction spends more than its outputs pay. Wallets estimate this network fee from transaction size and the selected fee rate. It is separate from a service's withdrawal charge; sending more LTC does not automatically mean a larger fee.
For example At an illustrative 2 litoshis per virtual byte, a 200-vB transparent transaction pays 400 litoshis, or 0.000004 LTC.
Common mistake Confusing the fee rate with the total fee or reading an exchange withdrawal charge as the miner fee.
A platform where users can buy, sell, and trade cryptocurrencies for fiat money or other digital assets. Major exchanges include Coinbase, Binance, and Kraken.
For example After buying LTC on a custodial exchange, you request a withdrawal if you want it sent to your own wallet.
Common mistake Assuming an account balance means you possess the private keys, or overlooking the selected withdrawal network.
A charge a service applies when you move LTC out of your account. The service sets its own fee and minimum; the quoted charge may differ from the miner fee of the transaction it broadcasts. Check the amount the recipient will receive before confirming.
For example If a service deducts a hypothetical 0.001 LTC fee from a 1 LTC withdrawal, the recipient receives 0.999 LTC; other services may quote the debit differently.
Common mistake Assuming an exchange charge is the network's fixed fee, or confirming without checking the final recipient amount and minimum.
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.
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.
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.
Segregated Witness: a change to transaction serialization and validation that separates witness data, fixes certain transaction-malleability issues and changes capacity accounting. Litecoin activated it in May 2017.
For example An ltc1q receiving address uses a SegWit format; the sender still needs to check that its service accepts that address.
Common mistake Assuming every wallet supports every address format, or that SegWit guarantees a fixed confirmation time.
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.
An address your wallet uses to receive the leftover LTC when it spends an input larger than the payment and fee. The change stays under your wallet's control. Wallets usually choose this address automatically.
For example Spend a 1 LTC input to pay 0.3 LTC with a 0.00001 LTC fee: the remaining 0.69999 LTC can return to your wallet as change.
Common mistake Assuming an unfamiliar second output is a second payment to the recipient; first check which outputs your wallet owns.
The process of using computational power to validate transactions and add new blocks to the blockchain. Miners are rewarded with newly created coins and transaction fees.
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.
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.
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.
A node's local collection of valid transactions waiting for a block. Nodes can see and keep different transactions, so there is no single global waiting room. A transaction seen in a mempool is still unconfirmed.
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.
A transaction output so small that a node's relay policy treats it as uneconomical to spend. The threshold depends on the output type and policy settings. It is not a universal minimum payment, and services may set different minimums.
For example A tiny leftover output may be rejected as dust even though your main payment is large enough.
Common mistake Copying one quoted dust number as a minimum for every address type, wallet, exchange or node setting.
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.
A method of replacing an unconfirmed transaction with a conflicting version that pays a higher fee under the receiving node's replacement rules. Wallet capabilities and node policy matter. A replacement is a new transaction, not an edit to an already confirmed block.
For example A wallet may construct a higher-fee version spending the original inputs; you must review its outputs and track the new transaction ID.
Common mistake Assuming every unconfirmed payment can be cancelled, or that a replacement guarantees acceptance, confirmation or a particular recipient outcome.
A fee-bumping technique that spends an output of an unconfirmed parent in a new child transaction with a higher fee. A miner may consider their combined fee and size. It requires an output you can spend and suitable wallet, relay and mining support.
For example A recipient may spend an eligible unconfirmed receipt in a higher-fee child while the original payment remains unchanged.
Common mistake Assuming any wallet can accelerate any payment, or that paying a child fee guarantees the parent will confirm.
An encoded destination for a payment. Common transparent Litecoin addresses begin with L, M or ltc1; MWEB uses a different address format. An address is not a bank account or proof of identity. Check network and wallet compatibility before sending.
For example To receive LTC, copy a Litecoin receiving address from your wallet and check it against the address shown to the sender.
Common mistake A valid-looking address does not prove that it belongs to the intended person or uses the network the sender selected.
Who controls the signing material and the process for moving funds. With a custodial service, the provider controls the relevant keys and you use an account. Self-custody places key and backup responsibility with you; an account password is not a private key.
For example An exchange withdrawal moves funds from the provider's control to an address whose signing keys your own wallet controls.
Common mistake Assuming an exchange balance and a self-custody wallet offer the same control, recovery process or withdrawal availability.
Transactions or data recorded directly on the blockchain. On-chain analysis examines publicly available blockchain data to derive insights about network activity, whale movements, and market trends.
For example A confirmed ordinary LTC payment appears in Litecoin blocks; an exchange moving balances between its own customer accounts may not.
Common mistake Assuming every account activity creates a blockchain transaction or that every large transfer is a trade.
A transaction receives its first confirmation when included in the accepted chain and another for each following block. Required confirmations depend on the recipient. Litecoin targets a 2.5-minute average block interval; individual waits vary.
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.
Content review recorded: 2026-10-22. 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.
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.
