Skip to content
TraceFast Docs

LP Liquidity

Open LP liquidity events in TraceFast →

LP Liquidity Events view

What it shows

Every time someone adds or removes liquidity from a DEX pool, the pool emits an event. LP Liquidity decodes those events across ~20 DEX protocols — Uniswap V2/V3/V4, Curve, Balancer, and the rest — into one chronological feed of who moved liquidity, where, and how much. Where the Pools view is organized by pool, this one is organized by event: the individual add and remove actions, ranked and filterable.

Three tabs frame the same stream around a different question:

  • Largest Removals — the biggest liquidity withdrawals in the window, sorted by size so exits stand out.
  • Whale Moves — the largest liquidity providers by position change: who is putting capital in, or pulling it out, at scale.
  • Outflow Monitor — pools showing a sustained net outflow, i.e. a potential drain signal.

How to read it

Liquidity leaving a pool is normal — providers rebalance constantly. What's worth attention is shape: a single outsized removal, or a steady one-directional outflow that the Outflow Monitor flags. Paired with a freshly-deployed pool and an unknown token, that pattern is the classic signature of a rug pull — the liquidity that made the token tradable being pulled out from under holders. On an established blue-chip pool the same outflow is usually just a large provider rotating capital.

Each event links to its pool and to the transaction that carried it, so you can go from "large removal" to the pool page and its trace in two clicks.

The Coverage column is the honesty check on every USD figure: it states what share of the event's legs carry a price. A removal shown at 100% priced is fully valued; a partial figure understates the true size, and the column says so rather than quietly rounding it in.

One transaction at a time

A row's transaction hash opens /defi/liquidity/by-tx/0x… — every liquidity event that transaction produced, which is how a multi-pool rebalance or a staged exit reads as one action instead of several unrelated rows.

Data & update cadence

Events are decoded from pool logs as blocks are ingested; the timeframe selector (24h / 7d / 30d) sets the window each tab aggregates over. The full history is paginated, running back tens of thousands of events.

Last updated 22 Oct 2026, 08:06 UTC · verified against TraceFast v1.0.261 · Markdown