Guide

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.

Can someone see your wallet balance from a Litecoin address?
On this page

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 happenedTotal ever received at AStill unspent at AOwner’s wallet balance
Before the first receipt000
A receives 0.600010.600010.600010.60001
B receives 1.400.600010.600012.00001
The owner spends the output at A0.6000101.70
Someone pays another 0.10 to A0.700010.101.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 testPublic amount and formatWhat our wallets established
Output 00.30 LTC, native SegWitThe shop controlled the destination.
Output 10.30 LTC, native SegWitThe 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Method and data

Downloadable data or code.

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.

Next scheduled review: 2027-02-20.

Sources saved with the review:

See the article body for source links and any downloadable materials. Editorial method · Corrections · Report an issue

Jarosław Wasiński
Editor-in-chief · Financial markets and Litecoin education

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.

Background, selected work and editorial responsibility →

Founder of MyBank.pl Financial education and market analysis Named editorial responsibility