Public facts and external identity data
Every full node can validate the same transaction graph. Observers see which outputs a transaction spends, which new outputs it creates and their amounts. An address does not contain a legal name, but a merchant, exchange, donation page or message can associate it with a person.
Once one link is known, earlier and later activity may provide more clues. The blockchain is persistent, so improved analysis or later disclosure can affect old transactions. Calling Bitcoin anonymous therefore promises more than the protocol provides.
Wallet behaviour creates clues
Reusing one receiving address gives observers an obvious common point. Spending several inputs together often suggests common control, and transaction structure can suggest which output is change. These are heuristics—reasoned inferences—not consensus facts, and special transaction designs can make them wrong.
Use a fresh receiving address, separate wallets or accounts for genuinely separate purposes, and meaningful local labels. Before combining outputs, consider whether their histories should become linked. A new address helps, but does not undo links created elsewhere.
- avoid address reuse
- preserve labels and purpose separation
- treat coin selection as a privacy decision as well as a fee decision
Looking up an address also discloses information
A public block explorer can learn that a visitor is interested in a particular address or transaction, alongside network and browser metadata. A wallet connected to a third-party server may reveal a broader set of addresses or filters through its queries, depending on its protocol.
Using one's own full node reduces reliance on an outside server for transaction and balance information. It does not by itself conceal all peer-to-peer network metadata. Tools such as Tor can reduce some network links, but configuration errors and behaviour can still reveal correlations.
Privacy techniques have costs and limits
Collaborative transaction techniques can make simple ownership heuristics less reliable, while adding coordination, fees and their own detectable patterns. Some services may restrict certain histories, and legal treatment varies. No technique makes it safe to publish all related identifiers.
Start with data minimisation: share only the address needed for one payment, avoid public screenshots of balances, and do not attach an extended public key to support requests. Choose wallet and node arrangements based on a stated threat model—who should not learn what—rather than a vague promise of anonymity.