Dexscreener
Dexscreener filters: Empty Shortlists and Conflicting Limits
Updated on
Dexscreener filters can leave a shortlist empty when no pair meets all active conditions. A pair that clears your liquidity floor may fail the volume requirement, age limit, or selected chain. Check the active view and its existing limits before treating an empty list as a fault.
The short version: An empty shortlist can be correct when no pair satisfies every active condition, even though each condition has matches separately.
A Visible Pair Missing From the Shortlist
A pair can appear in search while remaining absent from a filtered list because the two views answer different questions. Search locates a market; a shortlist includes markets that satisfy its conditions. Finding the pair therefore doesn’t establish that it should pass the screen.
The selected chain defines part of the candidate set before numeric limits matter. Sufficient liquidity won’t make a pair on an excluded chain qualify. The pair address and network identify the market whose values need to match your criteria.
Existing view settings also matter. New Pairs can carry age and liquidity restrictions before you add another condition. Inspect the visible settings rather than assuming that opening a different view gives you an unrestricted list.
Sorting changes the order of eligible rows. Filtering determines which rows qualify. Switching the ranking to volume won’t restore a pair that fails an active liquidity condition. This distinction explains why changing the order can leave the same empty screen.
Liquidity, Volume, and Pair Age
Liquidity describes the reported value held in a pool, while volume measures trading over a specified period. These quantities answer different questions. A pool can hold substantial liquidity during a quiet period, or record repeated trading against a smaller liquidity balance.
Pair liquidity data separates the dollar value from the base-token and quote-token amounts. Compare a dollar-denominated filter with the corresponding dollar value. A raw token quantity isn’t interchangeable with that value, even when both appear in the same market record.
Volume conditions need a matching time window. A daily volume requirement can’t be assessed using only a shorter activity interval. Likewise, a percentage price-change column isn’t trading volume. Read the field name and period together before deciding that a visible value clears the filter.
Pair age concerns the individual trading pool. It doesn’t establish the age of the underlying token. An age ceiling and a volume floor may each be reasonable screening choices, yet their combination can be restrictive: a pool younger than the selected volume window has had less time to accumulate activity within that window. That relationship doesn’t guarantee low volume, but it explains why the combined screen can exclude otherwise visible markets.
Can Valid Limits Still Produce No Results?
Valid limits can produce no results when their matching sets don’t overlap. Some pairs may clear the liquidity floor, while different pairs clear the volume floor. Neither group necessarily contains a pair that clears both. A minimum above the maximum for the same metric creates an impossible range if the interface accepts it. Even correctly ordered bounds can exclude every available pair. An empty result alone therefore doesn’t tell you whether the settings are contradictory, selective, or affected by unavailable data.
Isolate the Filter That Removes the Pair
If you expect a known pair to appear but the shortlist is empty, establish that the list can load before changing its criteria. A loading indicator or failed request doesn’t demonstrate that any pair failed a filter.
Keep the pair address, selected chain, active bounds, and observation time together. These details let you compare the same market throughout the diagnosis. No wallet signature or transaction is part of checking whether a pair satisfies a screening condition.
| Diagnostic Stage | Action | Condition for Continuing |
|---|---|---|
| Establish the starting view | Confirm that the list loads and the intended chain and pair match. | An unresolved loading failure prevents a filter diagnosis. |
| Isolate a restriction | Temporarily remove one numeric condition while keeping the others unchanged. | A returning pair must still satisfy every remaining condition. |
| Check the exclusion | Compare the pair’s corresponding value and period with the removed bound, then restore it. | The value must explain the exclusion; a missing value leaves the cause unresolved. |
| Keep the original settings available so that a temporary diagnostic change doesn’t silently become the saved screen. | ||
If removing a volume condition restores the pair, compare that condition with volume for the same period. Restoring the condition and seeing the pair disappear again supports that explanation, provided the underlying values haven’t materially changed between observations. Changing several bounds together would obscure which restriction mattered. If the pair stays absent, compare its values with each original condition. It may fail several conditions, so removing just one may leave it excluded.
Retry a failed load once the connection works. When the list loads normally and the pair clearly misses a required bound, repeated refreshing won’t correct that mismatch. If it meets every visible condition yet remains excluded, stop relaxing the screen and retain the settings and pair details for troubleshooting.
Why Does the Same Screen Change Over Time?
The same screen changes because its conditions are applied to changing market data. Pair age increases, trading activity changes, and reported liquidity can move. A pair can cross a boundary without any edit to your saved settings. Repeated checks therefore need both the settings and the time of observation.
Dexscreener uses a blockchain indexer to produce its screeners and market analytics. The displayed values describe the data available to that process. An older screenshot and a newly loaded list aren’t simultaneous observations. When a pair sits close to a bound, a small change can explain its disappearance; when the relevant field is unavailable, that comparison remains unresolved.
Screening Limits and the Stopping Point
A broader list establishes that more markets meet the revised conditions. It doesn’t establish that the revision suits your purpose. Liquidity and volume thresholds describe measurable properties, and lowering either threshold changes which properties the shortlist requires.
Before keeping the configuration, confirm the intended chain, the pair identity, each active bound, and the period attached to every activity condition. Check that minimum and maximum values form a possible range. Keep temporary diagnostic edits separate from the criteria you intended to use. Your next decision is whether to retain those criteria and accept an empty list, or deliberately change the screen’s requirements.
Questions people ask about Dexscreener filters
What Changes When I Filter by Market Cap Instead of FDV?
Market cap and fully diluted valuation can use different supply figures, so the same bound can admit different pairs. Dexscreener calculates FDV using total supply minus burned supply, multiplied by price. Market cap can instead use available circulating-supply information. Switching fields can change which pairs pass when their market cap and FDV differ; matching valuations produce the same result for the same bound.
Does a Liquidity Filter Require the Pool’s Funds to Be Locked?
A liquidity threshold doesn’t establish that a pool’s funds are locked. It tests the reported liquidity amount against your chosen bound. Restrictions on withdrawing liquidity are a separate property that the amount alone cannot demonstrate. A pair passing this filter therefore hasn’t also passed a liquidity-lock check.
How Are Buy and Sell Count Limits Different From Volume Limits?
Buy and sell count limits measure transaction counts, while volume limits measure the value traded during the relevant period. Large transactions can produce substantial volume without many transactions. Separate requirements for buys and sells can also exclude a pair whose activity is concentrated in one direction. Match each condition to its own field and time window.
Can Different Pools for the Same Token Pass Different Filters?
Different pools for the same token can have different liquidity, activity, and creation times. A condition can therefore admit one pool while excluding another. Keep the pair address attached to the values you’re checking. Using liquidity from one pool to explain why another should qualify would combine separate market records.
Will a Saved Filtered View Preserve the Same Pair List?
A saved filtered view doesn’t freeze the qualifying markets. Its stored settings describe selection conditions, while the pairs that meet them can change. For a useful record of an earlier result, retain the observation time and pair addresses alongside the settings. Reopening those settings later cannot recreate the earlier market state.