Liquidity is the depth behind every displayed price.
See what pool depth can explain, how reserves change, and why a price quote is never the whole market.
Liquidity Radar is designed around a simple idea: token activity is easier to interpret when pool conditions are visible. A pool’s reserves, fee model, and trading route affect how much a swap moves the price. This preview explains those mechanics but does not query a live decentralized exchange or index pool events.
Liquidity is the ability to trade near a price
In a decentralized exchange pool, liquidity is represented by assets deposited into a smart contract according to a pool design. A constant-product pool, for example, uses two reserves whose product is constrained by the pool’s formula. A trade changes the reserves and therefore the implied price.
A displayed token price may come from the most recent small trade. It does not mean that an order of any size can execute near that price. Depth across one or more pools, fees, routing, and current reserve ratios all matter.
Reserve size shapes the cost of a swap
A deeper pool generally absorbs a given order with less price impact than a shallow pool, assuming other conditions remain similar. The total value of reserves is only a rough starting point: token volatility, pool composition, route availability, and concentrated liquidity ranges can change the practical depth.
For analysts, it is useful to compare estimated order size against reserves rather than rely on a single “liquidity” number. The pool address and observation block should be visible because reserves can change from one block to the next.
Additions and removals need transaction context
A liquidity addition can increase available reserves, while a removal can reduce them. These actions are visible as contract events when the pool design emits the relevant logs. A change in reserves can also result from ordinary trading, fees, rebasing behavior, or token-specific transfer rules.
A monitoring tool should distinguish a liquidity-provider action from a reserve movement caused by swaps. It should identify the exact pool and transaction and avoid treating every decrease in one reserve as evidence of a rug pull.
The location of liquidity matters
Liquidity may be split across multiple pools, fee tiers, or exchanges. A token can appear liquid in one venue while most activity routes through a different pool. Concentration in one pool increases dependency on that pool’s availability and contract behavior.
Pool comparisons should state how values are normalized and whether the total includes stablecoins, wrapped assets, or only a selected pair. A chart should not aggregate unlike pools into a precise-looking total without showing the assumptions.
Separate expected price movement from execution cost
Price impact is the estimated change in pool price caused by a trade under a simplified model. Slippage is the difference between the expected and actual execution, which can be caused by market movement, ordering, route changes, or transaction timing. Fees and other pool-specific mechanics add further cost.
The Simulator offers a local hypothetical calculation using a clearly stated constant-product assumption. It is a learning aid, not a transaction quote or routing engine. See Dump Detector for ways unusual activity could be considered alongside pool depth.
A reserve change is a question to investigate
Imagine a pool begins with ample reserves and an LP removes part of one side. A later order may now move the price more than before. In another scenario, a new pool is created and attracts early liquidity, but its depth may be concentrated in a narrow range or controlled by a small number of providers.
Neither scenario is automatically malicious. Review the contract, pool events, provider positions where available, and independent sources. The Security & Transparency page explains why a liquidity observation cannot certify a project as safe.
Good questions deserve clear answers.
These notes reflect the current prototype status. For product details, follow the linked guides and their stated limits.
Does a high liquidity number make a token safe?
No. Liquidity can change, be concentrated, or exist in a pool with other risks. It is only one part of an analysis.
Can this page show live BNB Chain pools?
Not yet. No DEX data source is connected. The graphics and examples are explanatory.
What is slippage?
Slippage is the difference between an expected and realized execution price, often due to market movement or execution conditions.
THE INTELLIGENCE BEHIND EVERY MARKET SIGNAL.
Stay ahead by staying curious. Verify the event, question the interpretation, and keep the limits in view.