Can someone see your wallet balance from a Litecoin address?
An address in our Litecoin test showed zero while its wallet held 1.70 LTC. Follow four payments to see exactly what a customer can learn from your address.
Dotted-underlined terms open a quick definition. Close it to keep reading.
You send a customer a for an invoice. They can look it up, see how much has arrived there and follow those coins when they move. Can they also see how much Litecoin you have? A normal receiving address reveals the public activity at that address. To work out your whole balance, the customer would also have to know which other addresses and outputs belong to you.
We put that distinction to a test. An address received 0.60001 LTC. A few later its balance was zero, its original payment was still confirmed, and the wallet that owned it had 1.70 LTC. The most revealing detail was the outgoing transaction. It sent exactly 0.30 LTC to each of two destinations. Which one was the shop? A person who had paid the original invoice could see both amounts. The shop and our wallet each had one extra piece of information.
All figures in the experiment are test coins. The instructions for reading a receipt below apply to ordinary transparent Litecoin payments, where the inputs, output amounts and destinations can be inspected on the public chain.
What can the person who pays you actually see?
Give someone an ordinary Litecoin receiving address and they have something they can keep looking up. They can see confirmed payments to it, the amounts, and which of those specific outputs are still unspent. If you spend one, they can open the transaction that used it and see where the transaction created new outputs. An output is a piece of LTC assigned to a spending condition. The address is how your wallet tells someone which condition to pay.
A customer also knows something the never had to record. They know you sent them that address with invoice 104. They may have your business name, the agreed price and the email thread. Another person looking at the very same transaction might have none of that context. Put the address on a public donation page and every visitor can make the connection between the page and the address.
The address itself gives the customer no signing authority. They can send LTC to it and observe what happens. Spending its outputs requires satisfying the spending conditions. Likewise, the transaction has fields for amounts and scripts. Your wallet name, the name in your address book, and the list of other addresses you control live elsewhere. Litecoin Core’s transaction structures.
Five snapshots of one address and its wallet
We created three disposable wallets in Litecoin Core 0.21.5.8. One funded the experiment, one received payments and one played the shop. The receiving wallet generated address A for a customer, address B for another receipt and a fresh . We mined each transfer into its own block before taking the next reading. Here is what someone looking only at A could see alongside the owner’s wallet total.
Measured after each block. All amounts are in test LTC.
What just happened
Total ever received at A
Still unspent at A
Owner’s wallet balance
Before the first receipt
0
0
0
A receives 0.60001
0.60001
0.60001
0.60001
B receives 1.40
0.60001
0.60001
2.00001
The owner spends the output at A
0.60001
0
1.70
Someone pays another 0.10 to A
0.70001
0.10
1.80
The third row is easy to miss. From the perspective of address A, absolutely nothing happened when B received 1.40 LTC. The wallet owner saw the new payment immediately after the block. A reader with only A would need some independent reason to connect B with the same owner. Anyone could look up B if given the address. The missing information is the connection between A and B.
The last row is what makes a widely shared donation address a different proposition from a one-off invoice address. A past donor can revisit A later and see the new 0.10 LTC receipt. They can also see that deposits to A have totaled 0.70001 LTC. Calling that figure the owner’s savings would miss funds held elsewhere. Calling it sales revenue would require another assumption about why each payment was made. Five snapshots and all four test transactions.
Two identical amounts. Which one was change?
Look inside the transaction that emptied A. It consumed the entire 0.60001 LTC output. We asked the wallet to sign a transaction paying 0.30 LTC to the shop and sending 0.30 LTC back to an address the owner controlled. The remaining 0.00001 LTC paid the . That is 1,000 . There was one input and there were two outputs.
The same transaction viewed through the chain and the two test wallets
Output in this test
Public amount and format
What our wallets established
Output 0
0.30 LTC, native SegWit
The shop controlled the destination.
Output 1
0.30 LTC, native SegWit
The owner controlled this fresh change address.
Try covering the last column. Could you reconstruct it from the amounts? Both outputs used the same script type and the same amount, and each had a different address. Their order was a choice in our test transaction. The shop could identify its output by matching the destination it supplied. The owner’s wallet could recognize its own change address. Someone with only the original invoice address had neither of those pieces of evidence.
This also explains the 1.70 LTC. The owner still controlled the 1.40 LTC received separately at B and the new 0.30 LTC of change. Add them and you reproduce the wallet total exactly. Treat both outgoing outputs as purchases and you double the shop’s actual sale. Treat the entire 0.60001 LTC input as money paid to the shop and you include both the change and the fee. How inputs and change work in Litecoin.
How to check a payment after the address balance goes to zero
Suppose a customer writes, “The address you gave me shows zero. Should I send the payment again?” Start with the original invoice and the from the sending wallet. A current balance answers what is left to spend today. The disputed event happened earlier.
Open the original transaction. Use the full transaction ID on a Litecoin explorer. For a public mainnet example you can practice with the sample in our transaction checker.
Find the output paying the invoice. Match the full destination and the LTC amount to the request. A single transaction can pay several people. A matching amount alone leaves room for a mistake, as the two 0.30 outputs show.
Check inclusion and . Record the block and, if needed, the output index, often labeled vout. If a later transaction spent that output, the original transaction can still be confirmed. Our first receipt had four confirmations at the end of the test.
Reconcile the order with the receiver. A merchant can match the output to its invoice. An can check its own deposit ledger. If the destination, amount and confirmation record already match, take those details to the receiver before considering another payment.
A useful support message fits on two lines. “My invoice was for [amount] LTC at [destination]. Transaction [TXID], output [index], paid that amount in block [height]. Could you check the order credit?” Send those details privately to the actual merchant. If you need to distinguish a network receipt from an exchange balance, use the confirmed-deposit guide.
What to share for an invoice, donation or balance check
For a one-off invoice, use the receiving address your wallet prepared for that payment and keep your own copy of the request. Someone paying that address gets a precise destination. A fresh address also gives you a clean record for matching the receipt later. On a , verify the full address on its trusted display before sending the invoice. Trezor’s receiving instructions.
For a public tip jar, decide whether a public running history suits the purpose. Publishing a single transparent address lets a donor see later deposits there and when particular outputs move. Two payments of the same amount could come from two people, or from one person twice. Keep any donor records or campaign totals you need separately. If you later publish a new address, the old page and its old receipts can still be associated with you.
For a bookkeeper, first establish what they need to reconcile. A receipt for one invoice usually needs a transaction ID, a particular output and the invoice. Exporting an account’s , often called an xpub, can give the recipient visibility into many addresses derived from that key, including later ones, depending on the branch and wallet configuration. That is a much broader disclosure than forwarding a single receipt. Our measured guide to Litecoin extended public keys.
For an exchange deposit, the service can already associate its assigned deposit address with your account through its own records. A public visitor sees on-chain activity at that address. Your trading balance, trades and account credit are entries the service keeps internally. If funds are subsequently moved from a deposit address, the address balance alone says nothing conclusive about what you can withdraw from your exchange account.
When one address tells someone more
If all your confirmed funds happen to sit at one shared address, its unspent total can equal your wallet balance exactly. It did in the second row of our table. Only the owner knew that A held everything at that moment. The equality stopped as soon as B received its separate payment.
Context can narrow the possibilities. A customer who also knows the shop’s address can recognize that payment. An invoice published alongside a transaction gives a stranger another clue. And when several earlier outputs are spent together, the transaction publicly links those inputs to the same spend. That can support an ownership inference, although multiple parties can cooperate on a transaction. Assigning a balance to a person requires accounting for how each address was linked to them.
Switching to a fresh receive address helps with the simple case of unrelated customers revisiting the same public address. Earlier public records and any identifying details you have already shared remain available. Litecoin’s optional MWEB extension uses confidential amounts and different address mechanics. The transparent address arithmetic in this guide applies to the ordinary payments we tested. Our fresh-address experiment and the Litecoin Foundation’s explanation of MWEB.
How to check our figures
We ran Litecoin Core 0.21.5.8 in regtest with zero network peers on November 22, 2026. At each of five we counted the confirmed outputs paid to A and scanned the current unspent set for A’s exact script. Both operations used chain data available without a wallet. We then compared the result with getreceivedbyaddress and the owner’s getbalances report. We mined each payment before sampling, so the owner’s trusted balance in this experiment contained confirmed funds. Core chain queries and Core wallet queries.
The downloadable results contain amounts in whole litoshis, the four transaction IDs, their blocks and both wallets’ ownership checks for the equal outputs. The replay script creates fresh test wallets, so a new run produces different addresses and hashes. Its assertions check the same amounts at the same heights. These are private-chain transaction IDs. The public mainnet checker above has its own example for practice. Download the measurements or inspect the reproducible test.
Litecoin (LTC)
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 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 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 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 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 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 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 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 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 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 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 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 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 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.
Content review recorded: 2026-11-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.