A Wallet Tracker Must Separate Swaps From Transfers

To tell whether a wallet bought a token or received a transfer, trace the transaction’s token movements and identify what the wallet gave up in return. A buy usually involves a swap: the wallet sends one asset into a decentralised exchange contract and receives another. A transfer moves tokens from one address to another without that exchange of assets. The wallet’s balance records the result, but the transaction record shows the path.

Start with the transaction, not the balance chart. Check the wallet address, the token contract and the chain, then open the transaction details. Look at the list of token transfers, which records assets moving between addresses, and the event logs, which record actions emitted by contracts. A token arriving alone is not enough to call it a buy. For background on how charting and swap views fit together, Poocoin’s guide to charts, wallet tracking and swaps covers the distinction in more detail.

What does a token buy look like on-chain?

A buy usually leaves evidence of an exchange in the same transaction. The wallet, or a contract acting for it, sends an asset such as a stablecoin or wrapped native token towards a liquidity pool or swap route. The route returns the purchased token to the wallet. A decentralised exchange router may split the trade across several pools, so the wallet can interact with a router rather than directly with the pool.

Read the movements as a sequence. Find the outgoing asset, follow it through the contracts, then confirm that the wallet received the token it was seeking. Gas is a separate network fee paid to process the transaction; it is not the purchase payment. Some routes also wrap or unwrap a native coin, or pass through an aggregator, so the sender and recipient shown on a single transfer line may be contracts rather than the trader.

How can you spot a transfer instead?

A transfer usually shows the token moving from a sender address to the tracked wallet, with no matching swap that exchanges another asset for it. The sender might be another person, a wallet the same owner controls, a distribution contract, or a bridge. The record establishes that tokens arrived; it does not establish why they were sent or who ultimately controls the sender.

Use these checks before labelling the activity:

• Compare the transaction’s incoming and outgoing token movements.
• Check whether a swap contract or route handled an exchange.
• Follow the sender address when the token arrived without a swap.
• Check for a bridge or wrapping step before treating contract movements as a trade.

Some transactions combine actions, and tokens can be transferred as part of a larger contract call. A transfer event alone does not rule out a swap elsewhere in the same transaction. Likewise, a wallet can receive tokens from a purchase routed through several contracts. Classify the full transaction, not one line in its event list.

What should a wallet tracker count as a buy?

A tracker should count a buy when the transaction shows the wallet exchanging value for the token, and keep a plain receipt in a separate transfer category. That rule is more reliable than treating every incoming token as a purchase. It also avoids mistaking a wallet reshuffle for new demand when the same owner moves tokens between addresses.

For a quick review, record the transaction link, the amount sent, the amount received and the route or sender involved. If the exchange is unclear, label it as an unclassified receipt until you can trace the other movements. A wallet tracker is a view of on-chain activity, not proof of a person’s intent. The useful distinction is concrete: a buy includes an exchange; a transfer records tokens changing addresses.