Your Litecoin wallet shows a balance. Why won't it send?
A correct balance can still lack eligible coins or a usable signer. Eleven controlled Core states show how to check what is missing before depositing more or reinstalling.
AI-generated editorial illustration. A visible coin, separate key and selection gate represent observation, signing access and coin eligibility; this is not a wallet screen or a permanent lock.
On this page
Dotted-underlined terms open a quick definition. Close it to keep reading.
Your Litecoin wallet shows 1 LTC. You enter a small payment and it says “Insufficient funds,” asks you to unlock the , or refuses to finish signing. Those messages describe different problems. Sending another deposit, increasing the fee or reinstalling the application can be the wrong response.
A displayed balance is an accounting view. A successful payment also needs eligible coins, sufficient signing authority and enough value for the recipient plus the fee. Start by finding which of those conditions is missing.
We reproduced the distinction in Core 0.21.5.8. The same confirmed 1 LTC appeared in an ordinary wallet and in a , but only the ordinary wallet could complete the signature. In another wallet, locking its single coin left the reported balance at 1 LTC while automatic payment construction failed. This guide uses those controlled results to build a practical diagnostic checklist.
Scope: ordinary transparent Litecoin in a wallet. An account, wrapped LTC on another chain and MWEB balances have additional rules. Our experiment used an isolated regtest , no network peers and no real money. It did not test a mobile application or a physical .
First establish where the balance is
Before changing anything, identify the application and the account or wallet currently open. A Litecoin exchange balance is a claim recorded by that service. Your self-custody wallet balance is its view of outputs associated with keys or scripts it knows. A 's balance is a third view: it does not establish that your current wallet can sign for that address.
Three screens that can all display “1 LTC”
Where you see it
What the number establishes
What to check before sending
Exchange account
The service credits your account with an LTC amount
Withdrawal availability, holds, minimum, charge and supported network
Self-custody wallet
The wallet recognizes value under its accounting rules
Confirmation category, selected coins, signing access and fee coverage
Explorer or watch-only view
The software can observe an address or relevant outputs
Whether you have the corresponding signer or complete recovery material
If the LTC is on an exchange, adding a hardware wallet to your computer does not make the exchange's balance locally spendable. A withdrawal is a separate action. If you are in a restored wallet, compare a known receiving address and identify the intended account before concluding that an empty or unusable view means the coins disappeared. See our tested wallet-discovery guide for that separate problem.
Five different reasons for a balance that cannot fund a payment
The table below selects stages from our 11-state experiment. “Reported value” identifies the relevant balance category rather than adding every column into a fictional spendable total. Every 1 LTC receipt here is a synthetic test payment.
Observed wallet states in Core 0.21.5.8 regtest
Test state
Reported value
What happened
Diagnostic distinction
Confirmed, owned output
1 LTC trusted
A 0.1 LTC candidate was funded, fully signed and accepted by local policy
The positive control
Watch-only copy of that address
1 LTC watch-only trusted; 0 LTC mine trusted
The copied view could not complete the signature
Observation is not signing authority
Confirmed output locked from selection
1 LTC trusted; default balance still 1 LTC
Automatic construction returned “Insufficient funds”
Coin eligibility changed; value did not disappear
Incoming external payment, zero confirmations
1 LTC untrusted pending; 0 LTC trusted
The output was visible but excluded from automatic funding
An incoming receipt was not yet trusted by this wallet
Encrypted wallet, authorization locked
1 LTC trusted
Funding worked; signing requested the wallet passphrase
Signing access was locked, rather than the coin being absent
Fresh block reward
50 regtest LTC immature
The reward could not fund the initial payment attempt
A mining reward has maturity rules that an ordinary receipt does not
A practical diagnostic order; not a measurement of error frequencies. Open full-size SVG.
A watch-only wallet can show the correct coins
A watch-only wallet contains enough public information to recognize certain destinations or scripts, but not necessarily the private signing material. That makes it useful for monitoring. It also makes its accurate balance a poor test of recovery success.
In our experiment we imported an ordinary wallet's address into a new wallet created with disabled. After confirming a 1 LTC receipt, the original wallet reported 1 LTC in its mine.trusted category. The copied view reported 1 LTC in watchonly.trusted. The watch-only wallet's default getbalance also returned 1 LTC: Core includes watch-only value by default for a wallet whose private keys are disabled. Nevertheless, it could not produce a complete payment signature.
That is a useful recovery check: “the balance is right” and “the wallet can authorize a spend” are separate questions. An application paired with a hardware signer may deliberately keep keys elsewhere. In that case, check the documented device connection and signing procedure. Importing an address or an into another app does not turn that view into a signing wallet.
Identify the signer, backup type and, where relevant, wallet policy. Do not paste a seed, private key or wallet file into a support website to convert a watch-only balance into spendable coins. Our recovery evidence and checklist distinguish the materials that restore a view from those that restore signing access.
A coin-selection lock is different from an encrypted wallet lock
These two locks produced different failures in our test. A selection lock told the wallet not to choose its one confirmed output. The balance remained 1 LTC, but listunspent returned no available outputs and automatic funding failed. Unlocking that restored construction without any new deposit.
By contrast, encrypting a separate wallet left the confirmed output available for transaction construction. The wallet could fund the candidate, but signing failed until its local authorization was unlocked. After the documented local unlock, signing completed. We then relocked authorization.
Two locks, two different checks
Lock
What it controls
What it does not establish
Coin-control or output lock
Which outputs this wallet selects for a payment
An on-chain freeze or a revocation of another copy of the signing keys
Encrypted wallet authorization lock
Whether this wallet may use its encrypted signing material now
That the coins moved, or that every recovery format uses the same password
Review why a coin was locked before unlocking it. You may have excluded an unsolicited receipt or kept funds from different activities separate. Do not bulk-unlock everything simply because a payment failed. Core's RPC selection locks are local wallet controls; their documented lifecycle is not a permanent restriction. Other applications can implement different persistence and interfaces.
A , a device PIN and an additional seed passphrase can have different roles. This experiment covers Core wallet-file encryption. It does not establish that changing one password restores a missing seed or that a hardware device uses Core's unlock procedure.
An incoming unconfirmed receipt may be visible but excluded
We sent 1 test LTC from a different wallet and deliberately did not mine a immediately. Core reported the receipt in untrusted_pending. Its output appeared in an inclusive unspent listing with safe: false, while default payment funding returned “Insufficient funds.” After one local block confirmed the same receipt, the wallet reported 1 LTC trusted and funded the candidate.
This result is narrower than “you always need one to send Litecoin.” Wallets can treat their own unconfirmed change differently from an incoming payment created elsewhere. , replacement conditions and application policy also matter. The demonstrated problem was an externally created, unconfirmed receipt in this Core configuration.
Check the receipt's and status with the transaction checker. A pending payment is not a completed withdrawal merely because an exchange has reduced its account balance. A confirmed transaction is also not proof that a service has already credited its customer's account. If the public transaction itself is delayed, use the pending-payment diagnostic guide before attempting a second payment.
Do not disable safety checks as the first response. First establish whether the payment has actually confirmed and whether the sending and receiving services use the same network.
Mining rewards have a separate maturity rule
A creates the block subsidy and collects the block's fees. Here “coinbase” is the transaction type, not the exchange of that name. An ordinary payment from a is not automatically a coinbase output just because was the source of the income.
Litecoin's pinned source defines a 100-block constant. In our wallet test, the isolated 50 LTC reward remained in the immature category at both one and 100 recorded confirmations. At 101 recorded confirmations, Core's wallet moved it to trusted value and could fund the candidate. Its wallet availability calculation uses the maturity constant plus one minus current depth. This is a precise report of Core wallet behavior, not a claim that every payment requires 101 confirmations.
We advanced a private chain with test-only block generation. The result is measured in chain depth, not elapsed minutes. Do not multiply a target block interval by a counter and treat the product as a guaranteed unlock time. A pool's own payout threshold, waiting period and withdrawal policy are additional service rules.
Check the amount and fee after checking the coins
Even a fully spendable 1 LTC balance cannot usually deliver exactly 1 LTC to someone else while also paying a positive network fee. An exact-amount transfer needs additional value for that fee. A send-max workflow instead reduces the recipient's amount to fit the available input budget.
In our companion experiment, six full-balance exact-amount constructions failed across three input counts and two declared fee rates. All six send-max alternatives constructed valid local candidates. That fixes a different problem from a missing key or a selection lock. The exact amount and send-max guide shows the receipt, change and fee for each approach.
Check total fee and fee rate separately. A wallet's transaction preview is the relevant place to confirm the actual recipient amount and debit. An exchange's fixed withdrawal charge is a service price; it need not equal the network fee on the resulting transaction.
A diagnostic order that avoids unnecessary changes
Identify the location. Record the application, wallet or account, asset and network. Is this self-custody, watch-only or a service balance?
Check the receipt. Find its transaction ID, confirmations and category. Separate pending and immature value from available coins.
Inspect selection. Does manual coin selection restrict the input budget? Are relevant outputs intentionally locked?
Identify signing access. Is the correct device connected? Is local authorization locked? Do you have signing material rather than only a public view?
Check fee coverage. Does the selected value cover the exact recipient amount plus the final fee? If using max, inspect the reduced recipient amount.
Check the final status. A constructed or signed candidate is not necessarily broadcast. Record the actual transaction ID after sending and verify its outcome.
If you use Core's console, the following are read-only inspection commands. Select the intended wallet first. Their output can contain addresses and transaction details; do not publish it casually.
These commands do not unlock a wallet or spend money. A zero-length listunspent result alone does not prove a zero wallet balance: our selection-lock case is the counterexample. Inspect the balance categories and locks together.
Download a blank diagnostic record to keep the exact error, balance category and next check. It has no field for a seed, private key, wallet file or password. If you ask legitimate support for help, start with the application/version, public transaction status and exact non-secret error.
What we tested and how to reproduce it
The release contains 11 recorded wallet states and a shared payment-construction experiment. Across both parts, 103 executable assertions passed. All receipts and rewards are synthetic regtest coins. Wallet keys were generated temporarily and are not published. The source node used Core 0.21.5.8 with no peers; the script starts a new temporary directory rather than reusing a user's node.
The payment portion contains 18 fully signed candidates accepted by local regtest mempool policy, six rejected constructions and one selected send-max transaction actually mined. The offline analysis script independently decodes the exported signed transaction bytes to recalculate sizes, output totals and fees. That arithmetic check does not validate signatures or independently recreate wallet ownership.
Released 3 October 2026, Europe/Warsaw; the results file records the exact UTC test time. Research, code and drafting used AI assistance. The cover and figures are original explanatory diagrams, not wallet screenshots. No independent external review, mainnet transfer or hardware test is claimed. Send corrections 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 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 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 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 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 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 tool showing its indexed view of public blockchain data, which cannot reveal a service's internal account status.
A website or app that indexes blockchain data so you can inspect blocks, transactions and outputs. It reports its own data view. Looking up a public transaction needs no private key, and an explorer cannot see a service's internal account-crediting decisions.
For example Look up a transparent Litecoin TXID to check the destination output, amount and reported confirmations.
Common mistake Entering recovery words to track a public transaction, or treating one explorer's missing result as proof that no payment exists.
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 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 An extended public key for deriving related addresses in compatible software; it cannot sign alone and can reveal wallet activity.
An extended public key lets compatible software derive a group of related public keys and addresses without their private keys. It cannot sign by itself, and it does not reveal every possible wallet branch. Sharing it can still expose related receiving and change activity.
For example A watch-only service can derive new addresses from an account xpub without receiving the account's private signing key.
Common mistake Treating an xpub as harmless to publish widely or as a substitute for the secret material needed to restore signing authority.
In brief A transaction ID plus an output number, identifying one specific output of a transparent transaction.
The pair that identifies one output of an ordinary transparent transaction: its TXID and zero-based output index, often called vout. One transaction can create several outputs, so a transaction ID alone does not identify which one you mean.
For example TXID plus vout 0 and the same TXID plus vout 1 identify different outputs, even if both use the same receiving address.
Common mistake Assuming the recipient is always output zero or treating an address balance as the state of one specific output.
In brief A wallet-specific secret that can unlock stored keys or change the seed derived from recovery words.
A secret whose role depends on the wallet. A local encryption passphrase unlocks stored signing material. A BIP39 recovery passphrase is combined with recovery words to derive a seed. Changing the local unlock password does not by itself change that BIP39 recovery setup or move coins.
For example A typo in a BIP39 passphrase can derive a different valid wallet, whereas a wrong local encryption passphrase normally fails to unlock the file.
Common mistake Treating an app password, device PIN and recovery passphrase as interchangeable, or assuming a password change invalidates every old backup.
Compare: Wallet password vs recovery passphrase
Wallet Encryption
An encryption password unlocks a particular wallet's stored secrets; it does not replace a missing backup file or encrypt blockchain records.
Passphrase
A BIP39 recovery passphrase is used with recovery words to derive a seed; a different passphrase derives a different valid seed.
One example An incorrect unlock password is rejected by an encrypted Litecoin Core wallet; an incorrect BIP39 recovery passphrase can instead produce an empty-looking wallet with different addresses.
Remember: Check each secret's role in the original wallet: changing a local encryption password does not change a BIP39 recovery passphrase or move the coins.
In brief A linked record of transaction blocks that Litecoin nodes validate, choosing a valid chain by accumulated mining work.
A ledger of cryptographically linked blocks. Litecoin full nodes validate proposed blocks against consensus rules and select among valid chains by accumulated proof of work. Recent blocks can be reorganized, so confirmation depth matters.
For example A block explorer reads the chain so you can inspect where a transparent transaction was included.
Common mistake Assuming an explorer listing proves the sender's identity or that a recent block can never be replaced.
In brief Password protection for a wallet's stored secrets, separate from a recovery passphrase and unable to replace a backup.
Protection of a wallet's stored secrets with an encryption password. It does not encrypt blockchain records or replace a backup. A wallet-file password is distinct from a BIP39 passphrase, which changes the derived keys.
For example Unlocking an encrypted Core wallet allows signing for a limited time; it does not move its LTC.
Common mistake Assuming a wallet-file password can recover a missing file, or protects a seed phrase already exposed elsewhere.
Compare: Wallet password vs recovery passphrase
Wallet Encryption
An encryption password unlocks a particular wallet's stored secrets; it does not replace a missing backup file or encrypt blockchain records.
Passphrase
A BIP39 recovery passphrase is used with recovery words to derive a seed; a different passphrase derives a different valid seed.
One example An incorrect unlock password is rejected by an encrypted Litecoin Core wallet; an incorrect BIP39 recovery passphrase can instead produce an empty-looking wallet with different addresses.
Remember: Check each secret's role in the original wallet: changing a local encryption password does not change a BIP39 recovery passphrase or move the coins.
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 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 Choosing the available transaction outputs a wallet will spend to fund a payment and its fee.
The process of choosing which available outputs a wallet will spend to fund a transaction and its fee. Different selections change the number and types of inputs, the change output and spending costs. Wallets can apply different selection strategies; manual coin control lets the user influence the choice.
For example To pay 0.7 LTC, a wallet might use one 0.9 LTC output or combine smaller outputs, leading to different input counts and change.
Common mistake Assuming the wallet balance is one coin or that the smallest possible input count is always the wallet's only objective.
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 A block's special first transaction, used to claim newly created LTC and fees rather than spend ordinary earlier outputs.
The special first transaction in a block through which its creator can claim the allowed block subsidy and transaction fees. It does not spend ordinary previous outputs. Its spendable outputs are subject to coinbase maturity. This protocol term is separate from the similarly named exchange.
For example A block explorer shows a mining reward in the block's coinbase transaction. A later pool payout can be an ordinary transaction spending matured coins.
Common mistake Assuming an exchange withdrawal is a coinbase transaction because of the service's name, or treating newly mined outputs as immediately spendable.
In brief A service that coordinates miners' work and pays them under its own reward scheme and fee rules.
A service that coordinates mining work and pays participants according to its reward scheme. Fee handling, payment timing, variance and the treatment of merged-mining rewards depend on the operator's rules.
For example A pool can make payouts more regular than solo mining, but its fees and payment scheme affect the result.
Common mistake Assuming all pools pay the same amount for the same displayed hash rate or include the same merged rewards.
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 The rules nodes use to check transactions and blocks, with Litecoin using proof of work to choose among valid chains.
Rules used by nodes to decide which transactions and blocks are valid. Litecoin uses proof of work to select among valid chains. Miners propose blocks, but validating nodes also enforce the rules.
For example A full node rejects a block that breaks its validation rules even when a miner has done proof-of-work calculations.
Common mistake Thinking that miners can make any transaction valid merely by including it in a block.
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.
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.
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.