How do you find the transaction that killed a token's liquidity?

05 October 2026

The transaction that killed a token's liquidity is usually a single wallet action: a large sell order, a liquidity pool withdrawal, or a token transfer that drained the pool. You can find it by reviewing the token's trading history on a blockchain explorer, focusing on the moment the price collapsed and volume dried up.

What to look for

A token's liquidity dies when the pool it trades on no longer has enough of one asset to complete swaps. The killer transaction is the one that either removes a large chunk of the pool's reserves or sells so heavily that the remaining liquidity becomes practically unusable. These transactions share common traits:

• Large sell orders that cause a sudden price drop, often visible as a vertical line on a chart.
• Liquidity withdrawals where the deployer or a privileged address removes tokens from the pool.
• Token transfers that move a large supply to an exchange wallet or a dead address, signaling an exit.

Step-by-step method to find it

1. Get the token contract address

Find the token's contract address from a source like the project's website, a block explorer (Etherscan, BscScan, Solscan), or a DEX aggregator like Dexscreener. Avoid copying from unverified chat messages.

2. Open the token's block explorer page

Paste the contract address into the relevant block explorer. Look for the "Holders" or "Token Transfers" tab. Most explorers show the latest transactions first, but you need to go back to when the token was active.

3. Find the peak trading period

Use tools like Dexscreener, DEXTools, or the explorer's own chart to identify the date and time when the token had its highest price or trading volume. This is usually just before the crash. Note the block number or timestamp.

4. Scan transactions around that time

On the block explorer, filter by "Token Transfers" and scroll to transactions near the peak. Look for:

• Outbound transfers from the liquidity pool contract to any address. This is often the "removeLiquidity" action. The pool address can be found on Dexscreener or by checking the token's trading pairs.
• Unusually large transfers to an exchange or a new wallet. If a wallet that held a huge percentage of supply suddenly moves tokens, it signals a planned exit.
• A series of small sells that accelerate into one large sell. The final large sell often empties the order book or exhausts the pool's reserve.

5. Identify the killer transaction

The killer transaction is usually the one that:

• Removes the majority of the liquidity pool's base asset (e.g., the ETH or BNB side).
• Sells enough tokens to push the price below a critical threshold where the pool becomes one-sided (e.g., 99% of the pool is now the token, not the paired asset).
• Transfers the entire deployer's token supply to a dead address or a fresh wallet.

6. Verify by checking the pool's state

After finding the transaction, check the liquidity pool's balances before and after that block. Many explorers let you view the pool's reserve history. If the paired asset (e.g., ETH) dropped to near zero, that transaction is the killer.

Common patterns in killer transactions

• Rug pull: The deployer calls removeLiquidity on the DEX contract, draining both tokens and the paired asset. The transaction shows a transfer from the pool to the deployer's wallet.
• Dump: A single wallet sells a massive amount of tokens in one swap. The transaction shows a "swap" with an output of nearly zero of the paired asset.
• Supply transfer: The holder moves tokens to a exchange or a burner address, crashing confidence. The transaction is a simple transfer, often to an address with no prior activity.

What to check after finding it

Once you identify the transaction, look at the wallet that executed it. That wallet may have received the stolen funds or be linked to other dead tokens. Check if the same wallet has similar patterns in other projects. This can help you spot repeat offenders.

Why you might not find a single killer transaction

Not every token dies in one dramatic move. Some lose liquidity gradually through multiple small sells or fee accumulation. In those cases, no single transaction matches the pattern. Instead, the token's liquidity decays until swapping becomes impossible. For these tokens, the "killer" is the cumulative effect of many transactions, not one event.

If you cannot find a clear killer transaction, the token likely died from slow adoption or a failed project, not a single malicious action. The patterns described here apply most reliably to tokens that had active trading and then suddenly stopped.

Back to dead tokens