How to Check Token Volume on Solscan After a Session

To check token volume on Solscan, open the token's mint page, read the transfers list and the holder count, and compare them with figures you wrote down before the session. Start with the Solscan link the console shows for your fee payment, then, once the token trades in a pool, read volume, transactions and makers on DexScreener. Ten minutes and a notepad are enough.

What does the payment link in the console prove?

Step 3 in the PumpCrest console shows a payment address, a Solana Pay QR code and the exact amount. Once you send the fee, the console watches that address on-chain and displays the confirmed transaction with a Solscan link. That link is your first piece of evidence, and it is the only transaction you sign, because the service is non-custodial by design.

Open the link and check three fields: the sender is a wallet you control, the recipient matches the address the console displayed, and the SOL amount equals the quote. Copy the signature too; it pins the session to a timestamp. For a 250 SOL target the flat 1% fee is 2.5 SOL, so the transaction should show 2.5 SOL leaving your wallet, plus the small network fee your wallet adds. If any field looks wrong, email support before doing anything else.

Which parts of the Solscan token page matter?

Paste the mint address into the search bar at Solscan and open the token result, not a wallet or transaction result with a similar string. The page header usually shows supply, holder count and the token program. Below it sit tabs for transfers, holders and, depending on the current layout, a DeFi or swap activity view. Tab names shift as Solscan revises its layout.

Reading the transfers list

Each row is a token movement between two accounts, with a signature, a time and an amount. During a session new rows arrive at uneven intervals with varied amounts, since order sizes are drawn at random inside your band. A 1,000-wallet session executes about 1,600 orders, so expect the list to grow by something on that order over the session, plus any other trades in the same window. Use a time filter or export if the layout offers one.

Reading the holders tab

The holder count is the number of accounts with a nonzero balance. Session wallets that sold their whole position no longer count, which is why the console shows an estimated unique-holder count of about 62% of wallets rather than all of them. On 1,000 wallets that estimate is about 620. Treat it as a planning figure, not a promise: the way holder counts build during a session depends on the buy share and the timing of sells.

How do you read volume on DexScreener once a pool exists?

DexScreener lists a token once it trades in a pool with at least one trade, as its token listing docs describe. For a current Pump.fun launch that pool is on PumpSwap after the curve completes; older graduations sit on Raydium. If the curve completes during a session, execution follows the token into its pool within the same session, and the pair page starts collecting data from that point.

On the pair page, the stats panel splits activity into windows such as 5 minutes, 1 hour, 6 hours and 24 hours. For each window it typically shows volume in USD, a transaction count with a buy and sell split, and makers, meaning distinct wallets that traded. Read the window that covers your session rather than the 24-hour figure by default. If you care about the trending picture after migration, makers is the figure to watch beside volume.

Two cautions. DexScreener prices volume in USD, so convert at the SOL price of the time before comparing with a SOL target. And trades that ran on the bonding curve before migration may not be reflected on the pair page, so a session that ran mostly pre-migration will look smaller there than on Solscan.

Which numbers should you write down before and after?

A baseline turns a screenshot into evidence. Note each figure with the time you read it, once just before the session starts and again shortly after it ends. The table lists what to record and where it lives.

Worked example: 1,000 wallets with a 0.10 to 0.40 SOL band average 0.25 SOL per order, so the target is 250 SOL. Expect about 1,600 orders and an estimated holder gain near 620. With comments at 20% density, about 320 comments should appear on the coin page, each from a distinct wallet. With favorites at 30%, about 300 wallets star the token.

A 10-minute check you can repeat

Run this as soon as the saved project shows the session as finished, and again a day later if you want to see what held.

1. Open the payment transaction (1 minute)

   Use the Solscan link from your saved project. Confirm that sender, recipient and amount match the quote, then copy the signature.

2. Load the token page (1 minute)

   Search the mint on Solscan, confirm the name and ticker match the coin you meant, and read the holder count.

3. Count transfers in the window (3 minutes)

   Filter or scroll the transfers tab between your start and end times. Note the approximate number of rows and whether the sizes vary.

4. Scan the holders list (1 minute)

   Before migration the curve account tends to sit near the top, and after it the pool account; that is normal. Note anything else holding an unusually large share.

5. Read DexScreener (2 minutes)

   If the token is in a pool, open the pair, pick the window covering the session and note volume, buys, sells and makers.

6. Compare with the plan (2 minutes)

   Put your notes beside the session settings: wallets, band, target and densities. Write down any gap larger than you expected.

What will the numbers not tell you?

On-chain data shows what settled, not who will hold next week, what price the token reaches or where it ranks. PumpCrest reports volume, transactions, holders, comments and favorites as they settle, and it never promises a trending position, a price move or a profit.

• Other trades mix into the same lists, so totals after the session include other traders, not only session orders.
• Holder counts fall when wallets sell to zero, so a reading a day later can be lower than the reading at the finish.
• Skipping the after-session check is one of the mistakes that waste a session, because you lose the baseline for the next run.

Keep one plain text file per session with the mint, the payment signature, start and end times, and both sets of numbers. It makes the next session easier to size.

Questions and answers

Written by the PumpCrest team

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.