DexScreener trending on Solana draws on inputs the site describes publicly, such as volume, transactions, unique makers, liquidity, holders, price change and social and trust signals, but it does not publish thresholds. After a Pump.fun token graduates and its pool has a trade, a volume session can add to the activity inputs. Liquidity decisions, social and trust signals and real price action stay with the team and the market.
Ground rules for reading trending
- Listing comes first: a pool and at least one trade. Trending is a separate, ranked view on top of that.
- DexScreener describes its inputs in public docs but not the cutoffs, so nobody outside can say what a given rank needs.
- A session adds settled volume, transactions, makers and holders; it does not set liquidity, the token profile or trust signals.
- Price change comes from the whole market, so a session can contribute to it but never control it.
When does a graduated Pump.fun token appear on DexScreener?
The DexScreener token listing docs describe listing as automatic: a token shows up once it is in a liquidity pool with at least one trade. For a Pump.fun token, that point arrives with graduation, when the bonding curve completes and the token moves into a PumpSwap pool, or a Raydium pool for older graduations.
Listing is not the same as trending. A listed pair has a page, a chart and a trade history. Trending is a ranked view that compares pairs against each other in a time window, and being listed says nothing about where a pair will rank.
What does DexScreener say goes into trending?
The trending documentation lists the kinds of signals the score draws on. Grouped roughly, they look like this:
- Market activity: volume, number of transactions and unique makers.
- Market structure: liquidity and holder data.
- Price: price change over the window being ranked.
- Community and trust: social signals and trust signals tied to the token and its profile.
What the docs do not publish is the threshold for any of these or exactly how they combine. Anyone who says a specific transaction count puts a token on the list is guessing. The workable approach is to treat the inputs as directions, not as a recipe, and to measure what you added afterwards.
Which inputs can a volume session add to?
A session produces settled trades from many wallets. Those trades appear on-chain and on the pair page like any others, so the activity inputs are where a session shows up.
| Published input | Can a session add to it? | What that looks like in practice |
|---|---|---|
| Volume | Yes | Target volume = wallets x average order; 1,000 wallets at 0.25 SOL average is 250 SOL |
| Transactions | Yes | About 1.6 orders per wallet, so 1,000 wallets is roughly 1,600 transactions |
| Unique makers | Yes | Fresh session wallets every run, each funded with a different amount |
| Holders | Partly | The console estimates unique holders at about 62% of wallets; it is an estimate |
| Price change | Contributes only | Preset buy share is 58% to 68%, but every other trader moves price too |
| Liquidity | No | Set by the pool and by whoever adds or removes liquidity |
| Social and trust signals | No | Profile, links, community and history belong to the team |
A worked example with the Big prints preset: 1,250 wallets at 0.40-1.20 SOL over 2 hours. The average order is 0.80 SOL, so the target is 1,000 SOL and the fee is 10 SOL at 1%. That comes to about 2,000 orders and an estimated 775 unique holders. Whether that is a lot depends on what other Solana pairs are doing in the same window, which no one controls.
Which inputs stay outside a session?
Three things sit outside any volume session, and in practice they often decide how a pair looks next to its neighbors.
Liquidity depth decisions
Pool depth after migration comes from the graduation itself and from anyone who adds or removes liquidity afterwards. A session trades against that depth; it does not set it. Thin liquidity also means larger price impact per order, which is why the pool comparison guide is worth reading before you choose an order band.
Social and trust signals
A complete token profile, working links, an active community and a clean history are team work. A session can post comments on the Pump.fun page, but that is a different surface from the social and trust signals DexScreener describes.
Real price action
Price change comes from everyone trading the pair. A buy-leaning session tilts its own flow, but one holder selling a large position can outweigh it in minutes. PumpCrest reports settled activity and does not promise a price move or a rank.
How should a team time a session around migration?
- Decide whether the session should start on the curve and carry through graduation, or start once the pool already exists.
- If you start on the curve, pick a session length long enough to cover the first hours after migration, when the pair page is brand new.
- Prepare the token profile, links and social posts before graduation, so the trust side is ready when the pair appears.
- After migration, check pool liquidity on the pair page, and message support if the order band looks too large for it.
- Keep someone in the community channels while the session runs.
How do you check what the session added?
Every order settles on-chain, so the check is the same as for any trade. After funding, the console shows your confirmed payment with a Solscan link, and saved projects in the browser list each order as awaiting payment, running or finished. For the trades themselves, open the pair page and the token on a block explorer; the Solscan verification guide walks through what to compare.
Questions and answers
How many transactions does a token need to trend on DexScreener?
No one outside DexScreener can say. The docs describe the kinds of inputs, not the thresholds, and other pairs compete for the same list in the same window. Treat any specific number you see quoted as a guess. Plan the session around what you can measure afterwards: settled volume, transaction count and the estimated holder figure.
Do more wallets mean more unique makers?
Generally yes, because each wallet that trades counts as a distinct maker on the pair, and session wallets are fresh every run. Going from 1,000 to 2,000 wallets at the same 0.25 SOL average doubles the target from 250 SOL to 500 SOL, and the fee from 2.5 SOL to 5 SOL, since it is a flat 1% of target volume.
Can a session raise the liquidity of my pool?
No. A session buys and sells against the pool; it does not deposit liquidity. Depth is decided at graduation and by anyone who adds or removes liquidity later. If depth is the bottleneck, that is a team decision outside the console. Thin depth also makes each order move the price more, which changes how you should set the order band.
Should the session run before or after the pair appears?
Both work. Starting on the curve means the session is already running when the pool opens, and execution follows the token into the pool inside the same session. Starting after migration means every order lands in the pool. Teams that want activity on a brand-new pair page tend to prefer the first, with a length that covers the hours after graduation.
Are there rules I should check before running a session?
Rules differ by country, and this guide is not legal advice, so check what applies where you and your team operate. On the product side, the console is non-custodial: it never asks for a seed phrase, a private key or a wallet connection, and the only transaction you send is your own fee transfer from a wallet you control.
Give a new pair page real activity
Set wallets, order band and length in the PumpCrest console, read the target volume and order estimate it shows, and fund only when the numbers fit the pool you are trading into.
We build the PumpCrest console and write these guides from the operator side: what a session spends, what settles on-chain and what a visitor sees on the board. Corrections are welcome at support@pumpcrest.com.