Direct answer

Look for repeated coordination, not one dramatic clue

Two wallets become interesting when they keep showing up together through direct transfers, shared sinks, exchange deposit reuse, or recurring timing patterns. A single overlap is often weak. A stack of overlaps is where confidence starts to build.

Signals that matter

  • Direct value movement between the two wallets or through short paths.
  • Shared downstream sinks that appear repeatedly, not just once.
  • Common exchange deposit reuse that lines up with other evidence.

How to review the match

  • Check whether overlap appears across more than one signal type.
  • Compare recent timing so the behavior looks coordinated rather than random.
  • Reduce confidence when the overlap only touches very common public endpoints.

Where analysts overreach

  • Calling two wallets “same owner” based on one transfer.
  • Ignoring bridges, routers, and large exchanges that create false overlap.
  • Skipping manual review once a tool produces a ranked result.

Interpretation

What a good result should do

A good linked-wallet result narrows the investigation. It should tell you where to look next, not ask you to stop thinking.

For research

Use the result to map wallet clusters, coordinated execution, side wallets, and fund distribution patterns around a strategy or actor.

For risk work

Use it to identify wallets that should share review priority because they look operationally connected, even if the final owner remains uncertain.

For DeepDegen users

DeepDegen highlights candidates, evidence, and recency together, which makes it easier to separate persistent links from incidental overlap.

FAQ

Questions behind this search

Can an on-chain tool prove two wallets have the same owner?

Usually no. Good tooling provides strong linkage clues, while final ownership claims still require broader context.

What is stronger than a one-off transfer?

Repeated overlap across direct transfers, shared sinks, exchange deposit reuse, and timing is usually much stronger than one isolated transaction.

When should I ignore a match?

You should be cautious when the overlap comes only from a public exchange path, a common router, or a single event with no repeated behavior.

Related guides