DEX screener ranking settings and trading pair order
DEX screener ranking settings change which trading pairs appear first by changing the measure used to order eligible pairs. Comparing the list before and after a change requires the same filters and reporting period. Otherwise, a different leading pair may reflect a different comparison rather than the selected metric.
Jump to a section
Change the ranking while keeping the comparison fixed
In this hypothetical comparison, a reader wants pairs ordered by trading volume rather than Trending. The selected view offers volume sorting and displays figures for the intended reporting period. The reader checks that volume is the active ranking and that the visible values run from larger to smaller.
Before changing anything, the reader records the network scope, active filters, reporting period and current ranking. The record also identifies the leading pairs by their pair addresses rather than their row numbers. In this hypothetical comparison, the network scope, filters and reporting period remain fixed while the reader selects descending volume order. The list now places larger reported volumes ahead of smaller ones, subject to ongoing data updates.
Suppose the former leading pair moves below another pair with greater volume in that period. The changed position matches the new ordering rule. It does not establish that either pair gained or lost activity during the comparison. The initial Trending position and the subsequent volume position answer different questions about the same eligible markets.
If the view does not offer volume sorting for the intended period, selecting a different period would change the comparison. The reader instead looks for a view that exposes the intended combination, then reapplies the original scope and filters. If that combination remains unavailable, the reader cannot compare volume rankings for the intended period under the original scope and filters. An available alternative can support a separate comparison once its different period is explicit.
Why can a pair disappear after a settings change?
A pair can leave the visible rows because its position falls or because the active view excludes it. Those causes require different explanations. Sorting changes precedence among eligible entries; filtering changes eligibility. Switching a discovery view may also introduce conditions that were absent from the starting list.
Lower position within the same list
A pair that drops below the visible portion has not necessarily stopped qualifying. Its new position may simply follow from the selected metric. The first screen cannot establish that an entry disappeared from the entire result set. Row numbers describe positions within a particular list, so they are unsuitable as permanent pair identifiers.
Different eligibility conditions
Network selection and active filters define the population that the ranking can order. Gainers views can include volume and liquidity conditions alongside their price-change focus. A pair with a large percentage increase may therefore remain outside that list. Comparing filter settings explains this exclusion more directly than repeatedly changing the sorting direction.
An empty result needs an eligibility explanation before an ordering explanation.
Choose the metric that answers the comparison
Volume, transaction counts and price changes describe different properties, so their rankings can disagree without any display error. The selected metric determines what a high position means. Secondary columns add context, but they do not replace the active ordering rule.
Volume and transaction counts
Volume measures traded value over a reporting period, while transaction counts measure trading activity by count. Larger individual trades can produce substantial volume without the highest transaction count. Neither ordering alone reveals how many independent people participated. Keep the period consistent when comparing these columns; otherwise, the difference mixes measurement choice with elapsed time.
Percentage changes and liquidity
Price-change rankings prioritize the size and direction of a price movement within the selected interval. Liquidity describes the assets available in a pool rather than the value already traded. These measures support different comparisons. A liquidity-based shortlist concerns pool funding, while a price-change list concerns movement. Neither column establishes the execution price for a proposed swap.
Choose the ordering rule before interpreting the leading rows. Calling a pair the strongest entry adds a judgment that the sorting metric does not supply.
Does Trending put the highest-volume pair first?
Trending does not necessarily put the highest-volume pair first. The Trending Score incorporates market activity and community engagement. Its inputs include trading measures, page visits and reactions, while the precise weighting remains undisclosed. A volume column cannot reconstruct that composite ordering.
Paid Boosts can temporarily increase a token's Trending Score without guaranteeing a particular position. Choosing volume answers the narrower question about traded value. It does not turn the resulting list into a security assessment or a forecast of future returns.
Keep the reporting period attached to its control
The interval attached to a ranking determines which period that ranking describes. The interface presents short and longer Trending intervals alongside separate columns for price changes. Similar time labels do not make those controls interchangeable. A Trending interval describes the selected ranking view, while a price-change column describes price movement over its own interval.
Record the metric together with its period rather than saving an isolated time label. This prevents a short-window Trending comparison from being mistaken for a price-change comparison with the same duration. Also distinguish aggregate activity figures above the list from the figures for an individual pair. A total for the selected market scope is not the volume of its first row.
Rolling windows change as newer activity enters and older activity leaves. Even unchanged settings can produce a different ordering later.
Read the final order at the precision shown
The active ranking label and relevant values together explain the displayed order more reliably than the identity of the leading pair. Descending numeric order places larger values first; ascending order places smaller values first. A list can satisfy the new rule while retaining some or all of its previous positions.
Rounded or abbreviated figures limit what the visible rows can prove. Two entries displaying the same shortened value may differ at greater precision. Their order alone therefore cannot establish a tie or reveal the platform's tie-breaking rule. Likewise, a figure that has not loaded cannot support a numerical comparison merely because its row already has a position.
A before-and-after record can identify the setting that changed, but it does not freeze the market between observations. When values update during the comparison, attribute only the demonstrated difference to the control. If the scope, period or underlying figures also change, the new list needs an explanation that includes those changes.
Everyday questions about DEX screener
Do ranking changes require a wallet transaction?
Changing the order of a market list does not require an onchain transaction. Ranking settings control how the interface presents market data. They do not buy a token, move funds or change a liquidity pool. A wallet signature request concerns a separate action and is not evidence that a sorting change succeeded.
How does descending order handle negative price changes?
Descending numeric order places a less negative percentage above a more negative percentage. It compares signed values rather than the absolute size of each movement. A list ordered this way can therefore contain falling prices near the top when the eligible entries all have negative changes. A leading position does not necessarily mean a price increase.
Can another viewer reproduce a ranking from a screenshot?
A screenshot can document an observed order but cannot ensure that another viewer reproduces it later. It needs enough context to identify the metric, direction, reporting period and active filters. Even matching those settings leaves the observation time different. Cropped images that omit the controls make it harder to distinguish a settings difference from changing market data.
Are browser-extension filters part of the native ranking settings?
Controls added by a browser extension are separate from the platform's native controls. An extension may change which rows it displays without changing the underlying ranking selection. When comparing results between browsers, distinguish extension settings from the settings visible in the platform itself. A control that exists only with an extension cannot establish a native feature.