How to send an exact Litecoin amount or your whole wallet balance
See where the recipient amount, change and fee go in 24 controlled constructions. Compare exact payments, fee subtraction and send max, with measured sizes and downloadable checks.
Dotted-underlined terms open a quick definition. Close it to keep reading.
You have 1 LTC and want to pay an invoice for exactly 0.4 LTC. A different day, you want to move the entire balance. Those are different instructions. If you choose the wrong fee option, an invoice can be underpaid even though your wallet shows that you sent the amount you entered.
For an exact payment, keep the recipient amount fixed and pay the fee in addition. For a send-max payment, the recipient normally receives the available input value minus the fee. A “subtract fee” option can also reduce a smaller entered amount. Read the recipient amount in the final preview rather than relying on the amount you first typed.
We built 24 controlled Core payment cases to measure the differences. Eighteen were fully signed and accepted by the isolated 's policy; six attempts to send the entire 1 LTC as an exact recipient amount failed. One selected send-max transaction was then mined and left its sending test wallet at zero. The worked figures below come from those transactions, not an approximate transaction-size formula.
This guide concerns ordinary transparent Litecoin. The inputs are native test outputs. It does not measure MWEB fees, withdrawal pricing, mobile app interfaces or current mainnet fee requirements.
Decide which amount must stay fixed
Start with the purpose of the transfer. A merchant invoice usually specifies what the merchant must receive. Moving funds between your own wallets may instead specify how much of the old wallet you want to empty. A budget can specify the maximum total debit, including the fee.
Match the instruction to the payment's purpose
Your intention
Amount that stays fixed
What absorbs the fee
Pay exactly 0.4 LTC
Recipient gets 0.40000000 LTC
Additional sender value; less change remains
Spend a total budget of 0.4 LTC
Total wallet reduction is 0.40000000 LTC
Recipient receives less than 0.4 LTC
Send all eligible coins
Selected input value is fully consumed, with no change
Recipient receives the input total minus the fee
The second row is what fee subtraction can do. It can be useful for a deliberate total budget, but it is a poor default for paying an exact invoice. A requested 0.4 LTC and a received 0.39999718 LTC are different amounts, even when the difference is small.
If you are paying an exchange deposit , inspect its minimum creditable amount as well. The amount arriving after fees must meet the service's current terms. A valid receipt does not override a provider's deposit minimum.
Follow the measured 1 LTC example
We funded a fresh test wallet with one confirmed output worth exactly 1 LTC. We then used a declared rate of 2 per . One litoshi is 0.00000001 LTC; the rate is an experimental setting, not a recommendation for today's network.
One P2WPKH input, 1 LTC budget, declared 2 litoshi/vB
Construction
Recipient
Change to sender
Fee
Wallet reduction
Exactly 0.4 LTC, fee additional
0.40000000 LTC
0.59999718 LTC
0.00000282 LTC
0.40000282 LTC
0.4 LTC with fee subtracted
0.39999718 LTC
0.60000000 LTC
0.00000282 LTC
0.40000000 LTC
Send max
0.99999780 LTC
0 LTC
0.00000220 LTC
1.00000000 LTC
Exactly 1 LTC, fee additional
No constructed payment
No change created
No fee paid
Construction rejected
The first two signed transactions measured 141 vB; the one-output send-max transaction measured 110 vB. Its smaller measured fee follows from a smaller transaction in this setup. It does not establish that every application's max button always saves the same amount.
Accounting from the one-input, 2-litoshi/vB regtest candidates. Open full-size SVG.
In the failed exact-1-LTC case, the wallet needed more than its 1 LTC input to preserve the recipient amount and pay a positive fee. It returned “Insufficient funds.” No transaction was broadcast and no was charged. Merely preparing another preview does not repeatedly pay a fee.
Why a 1 LTC input does not mean a 1 LTC payment
An ordinary transparent transaction consumes each selected previous output in full. It creates a recipient output and, if needed, a new controlled by the sender. The network fee is the difference between total input value and total output value.
An explorer showing a 1 LTC input has not demonstrated that the recipient was paid 1 LTC. Neither has a wallet history row necessarily separated the recipient payment from change. Inspect the destination's actual output and keep the fee separate. Our transaction checker helps inspect public outputs; it cannot infer every output's owner.
Change is normally managed by the wallet. Do not replace its change address with an exchange deposit destination or a stranger's address because a tutorial mentions “custom change.” The UTXO and coin-control guide explains that structure in more detail.
The same 1 LTC balance produced different send-max amounts
We repeated the experiment with 1 LTC split over three outputs and ten outputs. Every candidate explicitly used all outputs in its group; automatic input selection did not decide how many to spend. The three-input group contained 0.33333333, 0.33333333 and 0.33333334 LTC. The ten-input group contained ten 0.1 LTC outputs.
Measured send-max candidates; each starts with exactly 1 LTC
Inputs
Declared rate
Signed size
Fee
Recipient
1
2 litoshi/vB
110 vB
0.00000220 LTC
0.99999780 LTC
3
2 litoshi/vB
245 vB
0.00000490 LTC
0.99999510 LTC
10
2 litoshi/vB
719 vB
0.00001438 LTC
0.99998562 LTC
1
10 litoshi/vB
110 vB
0.00001100 LTC
0.99998900 LTC
3
10 litoshi/vB
245 vB
0.00002450 LTC
0.99997550 LTC
10
10 litoshi/vB
719 vB
0.00007190 LTC
0.99992810 LTC
Zero-baseline comparison of signed sizes in our frozen export. Open full-size SVG.
At the same declared 2 litoshi/vB, the ten-input sweep paid 1,218 more litoshi than the one-input sweep. That is 0.00001218 LTC. The ten-input transaction's measured size was about 6.54 times the one-input size, despite both wallets starting with 1 LTC.
The important variable here is the transaction structure, not the value of the wallet. Different script types, input counts, signatures and change outputs can change the final size. These measurements also explain why subtracting a remembered fee from a balance is less reliable than using an appropriate wallet preview.
This is not an instruction to consolidate coins before every transfer. Consolidation pays another fee now and can publicly link previously separate receipts. Our separate guide compares those tradeoffs. Use current fee information for context, then inspect the actual signed or final wallet quote.
“Send all” can mean all selected coins
A max button has to operate on a particular input budget. If has selected only part of the wallet, the result can empty that selection rather than the whole wallet. Pending incoming receipts, immature rewards, intentionally locked outputs and value can also sit outside the eligible budget.
Our send-max cases emptied their explicitly selected 1 LTC groups. We broadcast and mined just one selected sweep: the one-input, 2-litoshi/vB candidate. Its recipient received 0.99999780 test LTC and the source wallet's confirmed balance became zero. The other 17 signed candidates were policy-tested without broadcasting; their expected accounting follows from their recorded inputs and outputs.
A zero balance after a sweep is a snapshot, not a promise that the old wallet can never receive money again. An earlier address controlled by that wallet can still receive later payments. Check saved withdrawal addresses and recurring payout destinations before retiring it. Our receiving-address experiment explains why generating new addresses does not disable old ones.
If “max” is much smaller than the visible balance, first inspect eligible inputs and signing access. The companion balance-but-cannot-send guide tests those exclusions. Increasing the fee cannot supply a missing or unlock a coin-selection restriction.
Keep exchange charges and market conversions separate
The measured numbers above apply to a transaction. An exchange may quote a fixed LTC , enforce a minimum or combine multiple withdrawals into one transaction. Its interface can define an entered amount as a total debit or a net receipt. Check the actual labeled fields; do not assume its behavior matches Core's fee-subtraction option.
If an invoice is denominated in euros, there is another decision: which and validity period establish the LTC amount due? A reference-price calculation is not necessarily the merchant's executable invoice quote. Recalculate only according to the agreed terms, rather than silently reducing the amount because the market price moved.
Use the complete purchase-cost comparison when the route includes buying and withdrawing. For an already issued Litecoin invoice, the payment request and reconciliation tools help keep requested amount, actual receipt and acceptance status distinct. Those tools calculate and inspect; they do not connect to your signing wallet.
Check precision, minimums and the full destination
Transparent LTC amounts in this experiment are integer litoshi: eight decimal places. A rounded fiat display can hide a shortfall. The fee-subtracted 0.4 LTC example was 282 litoshi below the request, even if both screens rounded to the same currency value.
Record the invoice amount in LTC and inspect the actual output with enough precision. Do not repeatedly resend a tiny difference without checking the recipient's rules: a service may reject deposits below its minimum, and a very can encounter dust-policy limits. Our controlled dust-policy guide shows why there is no universal threshold for every script and fee configuration.
A valid address checksum does not authenticate the recipient. Compare the full destination with a request obtained through a trusted channel. If you use a , follow its documented display checks. A successful small test does not validate a substituted destination for the later larger payment.
Try the payment preview simulator
Start with a 1 LTC balance and a 0.4 LTC payment. Compare sending exactly 0.4 LTC, subtracting the fee from the amount entered, and sending your whole balance. See what the recipient gets, what you pay in fees, and how much of your balance remains.
Recipient receives
Network fee
Total taken from your balance
Balance remaining
This exercise uses the fee you enter and runs in your browser. Check the actual amount and fee in your wallet before approving a payment.
A final preview checklist
Purpose: exact invoice amount, fixed total budget or transfer of all eligible coins?
Destination: correct asset, supported network and full address from a trusted request?
Recipient: what amount will the recipient actually receive after any fee subtraction?
Debit: what value leaves your control after accounting for change and the fee?
Selection: does max apply to the whole eligible wallet or only selected inputs?
Minimums: does the final receipt meet the destination's current minimum and invoice terms?
Authorization and outcome: does the final signer display match, and did the transaction actually broadcast?
Download the blank payment-preview checklist. Keep a record of the agreed recipient amount and the actual . You do not need to disclose recovery material to check either.
If a recipient was underpaid, first agree how to settle the difference and retain both records. Do not assume a second transfer cancels or edits the first. The refund and underpayment guide covers that follow-up workflow.
Method, downloads and limits
The experiment used Core 0.21.5.8 on a fresh isolated regtest chain with no peers. It created three 1 LTC budgets with one, three and ten confirmed P2WPKH inputs. Each budget was tested at declared rates of 2 and 10 litoshi/vB, with four instructions: exact 1 LTC, exact 0.4 LTC, 0.4 LTC with fee subtraction and send max. That gives 3 × 2 × 4 = 24 construction cases.
The six exact-full-balance cases failed before broadcasting. Eighteen other candidates completed signing and passed that node's local -policy check. One sweep was broadcast and mined on regtest. Across the shared wallet-state and payment experiments, 103 assertions passed.
The 24-case CSV provides amounts in integer litoshi. The results JSON also contains the signed transaction bytes and selected input values. The offline analysis redecodes all 18 signed transactions, verifies their recorded identifiers and recalculates virtual size and input-minus-output fees. It does not validate signatures, independently prove the inputs existed or measure propagation.
See the reproduction instructions, complete package and checksums. Source behavior was checked against the pinned Core wallet RPC implementation, including the different units of feeRate and fee_rate. Our script uses feeRate in LTC per 1,000 virtual bytes: 0.00002 corresponds to 2 litoshi/vB. Copying the value between differently named fields would change its meaning.
The exact measurements belong to these signed transactions. Another wallet, script type or signature can produce a different size. Regtest acceptance is not a mainnet confirmation guarantee. No actual purchase, service withdrawal, MWEB transfer or hardware/mobile interface was tested.
Released 3 October 2026, Europe/Warsaw; exact test time is recorded in UTC. Research, code and drafting used AI assistance. The original cover and SVG diagrams illustrate measured accounting, rather than pretending to be application screenshots. No independent external reviewer is claimed. Report an error through our corrections page.
Wallet
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 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 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 transaction format and validation change that separates witness data and changes how block capacity is counted.
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.
In brief A single-key SegWit output type; Litecoin's ltc1q prefix alone does not distinguish it from P2WSH.
A SegWit version-0 output type that commits to a public-key hash. Spending it places the signature and public key in witness data. Its native Litecoin mainnet address uses ltc1q, but that prefix also covers P2WSH, so the prefix alone is insufficient for a precise fee model.
For example The fee estimator's native SegWit input option models P2WPKH. Check the wallet's actual script type before selecting it.
Common mistake Assuming every ltc1q output is the single-key P2WPKH type or confusing its witness bytes with full-price base bytes.
In brief A service for trading currencies or assets, whose custodial account balance does not give you control of its private keys.
A platform or service for buying and selling cryptocurrencies against fiat currencies or other assets. Trading methods, custody, supported pairs and withdrawal rules vary by service. A balance on a custodial exchange is an account claim; it does not mean you control the wallet's private keys.
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.
In brief An encoded payment destination whose network, owner and wallet compatibility still need checking.
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.
In brief Recorded in accepted blockchain blocks, unlike account changes a service may make only in its own records.
Recorded in the blockchain's accepted blocks. For transparent Litecoin, many transaction details are publicly visible, but an exchange's internal account changes need not create an on-chain transaction. Blockchain records alone do not establish an owner's identity or why funds moved.
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.
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 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 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 wallet-controlled destination for leftover LTC after spending an input on a payment and its fee.
Spending a transparent transaction output uses its whole value. After paying the recipient and fee, a wallet can send the leftover LTC to an address it controls. That destination is a change address. Wallets usually choose it automatically.
For example A fictional 1 LTC input paying 0.3 LTC with a 0.00001 LTC fee can return 0.69999 LTC to a wallet-controlled change output.
Common mistake Assuming an unfamiliar second output is a second payment to the recipient; first check which outputs your wallet owns.
In brief Government-issued money such as EUR or USD, including cash and bank deposits, separate from a wallet's displayed LTC valuation.
Government-issued money such as USD, EUR or GBP, whose value does not depend on redemption for a fixed quantity of gold or another commodity. It can exist as cash or bank deposits. An LTC price displayed in a fiat currency is a valuation, not an extra cash balance.
For example USD, EUR and PLN are fiat currencies; an LTC/EUR quote expresses one coin's price in euros.
Common mistake Confusing the fiat value shown by a wallet with an extra cash balance held in that wallet.
In brief An unspent output from an earlier transaction, used whole when selected for an ordinary transparent payment.
An unspent transaction output: a recorded amount from an earlier transaction that has not been spent. A transparent Litecoin wallet can select eligible UTXOs as inputs for a new payment. Each selected output is spent in full; value left after the payment and fee can return as change.
For example Fictional receipts of 0.4 LTC and 0.6 LTC can be two UTXOs even when a wallet shows a single 1 LTC balance.
Common mistake Assuming the displayed wallet balance is one indivisible account entry, or that spending an input sends all of it to the recipient.
In brief Wallet controls for choosing available transaction outputs to spend, affecting fees, change and links between payments.
Wallet features that let you inspect and choose which available outputs a payment spends. The selected inputs affect transaction size, change and which previous receipts become linked. Manual selection does not bypass signing, maturity or wallet-policy requirements.
For example Choose one suitable UTXO instead of combining several unrelated receipts, then review the resulting fee and change.
Common mistake Assuming manual selection guarantees lower fees or privacy, or that a visible but unavailable output can fund a payment.
In brief A wallet view that can show addresses and activity from public information but cannot sign a payment on its own.
A wallet view built from public information that can recognize addresses and transactions without holding their private signing keys. It can show a balance or help prepare a payment, but spending needs the appropriate signer or cosigners through a supported workflow.
For example Importing an address or xpub can reproduce a receiving view while leaving that wallet unable to sign on its own.
Common mistake Treating matching addresses or a displayed balance as proof that recovery also restored spending authority.
In brief Secret data a wallet uses to sign spending; one key may cover only part of a wallet and must never be shared.
Secret data used to authorize spending under the conditions attached to coins. In a simple single-key wallet, anyone with that key can spend the coins it controls. A wallet may manage many keys; never share them.
For example A wallet signs a spend using a private key; the recipient only needs your payment, not that secret key.
Common mistake Sharing a key with support or assuming one exported key necessarily backs up every address in a wallet.
Compare: Seed phrase vs private key
Seed Phrase
Recovery words used by many wallets to rebuild key material; the correct format, optional recovery passphrase and wallet settings still matter.
Private Key
A secret used to authorize spending under its key conditions; one exported private key is not necessarily a backup of every key a wallet uses.
One example A fictional simple HD wallet can derive several receiving keys from one recovery setup; exporting just one of those private keys does not preserve the others.
Remember: Identify the complete backup method for the original wallet, keep secret recovery material offline and never paste it into this website.
In brief Who controls spending access; with a custodial service, the provider controls the keys behind your account.
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.
In brief A service's charge for moving LTC out, which can differ from the network fee and reduce what the recipient receives.
A charge a service quotes for moving LTC out of your account. Its rules determine the fee, minimum and amount received. A service can batch several withdrawals into one transaction, so one customer's quoted charge need not match the transaction's network fee. Check the final account debit and recipient amount 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.
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 The quoted amount of one currency per unit of another, with direction, spread and fees affecting its use.
The amount of one currency or asset quoted for one unit of another. Pair direction matters: EUR per LTC and LTC per EUR are reciprocals. A reference conversion does not include every spread or service fee and is not necessarily an executable buy or sell offer.
For example At a hypothetical 50 EUR per LTC, 0.2 LTC has a reference value of 10 EUR before spreads and fees.
Common mistake Using a rate backwards, confusing a current reference with a historical transaction rate, or assuming the displayed conversion is what a provider will deliver.
In brief An output a node's relay rules regard as too small to spend economically, with no single universal amount.
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.
In brief A device designed to keep signing keys isolated while approving supported transactions, still requiring safe setup and backups.
A dedicated device designed to isolate signing keys and approve transactions through its supported interface. It still depends on correct setup, backups, supported software and careful review of the recipient and amount. Coins remain recorded on the blockchain.
For example A connected app prepares a payment while the hardware device displays details for you to verify before authorizing a signature.
Common mistake Assuming owning the device makes an exposed recovery phrase safe or removes the need to check what you authorize.
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 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.
Downloadable data or code · Controlled wallet / regtest · Beginner selection.
Content review recorded: 2026-10-03. 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.
24 controlled constructions with explicit equal 1 LTC budgets. 18 signed candidates policy-tested, six rejected and one sweep mined; no mainnet fee recommendation.
A one-input send-max candidate delivered 0.99999780 LTC from 1 LTC; the exact-full-balance construction failed before broadcasting.
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.