How to Verify Volume on Solscan for a Pump.fun Coin

Charts and dashboards show a number. Solscan shows the trades behind it. If you want to check a coin's activity yourself, whether it's your own launch, a run you paid for or a coin you're thinking of buying, the explorer has everything you need. It just doesn't add it up for you. We'll go through it tab by tab.

11 min read

To verify volume on Solscan, open the coin's token page, go to the DeFi Activities tab and filter to token swaps in your window. Each confirmed signature is a trade, each distinct signer is a trader, and the SOL side of every swap, summed, gives you the volume. Program IDs separate curve trades from PumpSwap trades.

Key points

  • Start from the token mint address, not from a link someone sent you.
  • The DeFi Activities tab lists swaps; the Transfers tab lists plain token movements.
  • Count only transactions with a Success status. Failed ones pay a fee but move nothing.
  • Unique traders means distinct signing addresses on swaps, not holder count.
  • Solscan exports the latest 1,000 records per CSV, so split long periods into shorter windows.

Why verify volume on Solscan at all?

Verifying volume on Solscan matters because every trade on a Pump.fun coin is a public Solana transaction, and Solscan is one of the easiest ways to read them. Volume on a coin page, a DexScreener chart or a bot's dashboard is a summary. Summaries use different time windows, different price sources and different rules for what counts. The ledger doesn't. If two sources disagree, the transactions settle it.

Who is this for? Creators as much as buyers. If you paid for a run, you should be able to see the trades land. If you're about to buy a coin, you might want to know whether a busy chart comes from many wallets or a handful. Same method, both cases. It takes about twenty minutes the first time and five after that.

What do you need before you start?

  1. The coin's mint address. Copy it from the Pump.fun coin page and check the first and last characters. Tickers repeat; mint addresses don't.
  2. A time range. Pick a clear start and end, for example the launch hour or the length of a run.
  3. A spreadsheet. Any one will do. You need to sum a column and count unique values.
  4. The two program IDs. The Pump bonding curve program is 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P. The PumpSwap AMM program is pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA.

Before you start, note which time zone Solscan is showing and which one any other tool uses. Pick one and stick with it, especially when you compare numbers side by side. Half the mismatches people report come from one source counting in UTC and another in local time.

Annoying, but easy to fix.

How do you find the right token page?

Paste the mint address into the Solscan search bar and pick the token result. Check the name and symbol, but trust the address. Copycat tokens often share a name with a busy coin, and a search by ticker can land you on the wrong one. The token page header shows the supply and the basic token details Solscan has indexed.

Below the header sit the tabs. Three matter for this job. Transfers lists every movement of the token between accounts, including mints and burns. DeFi Activities lists actions that went through DeFi programs, such as swaps and liquidity changes. Holders shows the current balance of each account. For volume, you'll live in DeFi Activities.

How do you filter trades in the DeFi Activities tab?

Open DeFi Activities and use the filter controls above the table. Solscan's own guide lists what you can narrow by: a date range, the activity type, the platform and the liquidity pool source. Set the date range to your window, then set the activity type to token swaps so liquidity events and other actions drop out, and from then on each row shows the signature, the time, the account, the two sides of the swap and the platform it ran through.

  1. Open the token page

    Search the mint address on Solscan and choose the token result, not an account or a similarly named coin. Copycat tokens often share a name with a busy coin, so trust the address over the ticker. The header then shows the supply, which for a Pump.fun coin is 1,000,000,000 tokens, a quick check that you're on the right page.

  2. Switch to DeFi Activities

    Switch to the DeFi Activities tab, which lists swaps and other actions that went through DeFi programs involving the token. Of the three tabs that matter here, Transfers shows plain token movements and Holders shows current balances, so neither gives you trades. For volume, DeFi Activities is the tab you'll work in from here on.

  3. Set the date range

    Use the date picker to set the exact start and end of the window you want to check, for example the launch hour or the length of a run. Pick one time zone and keep it, because local time against UTC can shift a whole hour of trades in or out of your count.

  4. Filter to token swaps

    Set the activity type to token swaps so liquidity adds, removals and other actions drop out of the table. From then on each row shows the signature, the time, the account, the two sides of the swap and the platform. Only rows with a Success status count, since a failed transaction moves no tokens or SOL.

  5. Narrow by platform if needed

    Narrow by platform when the coin graduated inside your window. Select the Pump.fun curve, PumpSwap or both: curve trades go through the Pump program and pool trades through the PumpSwap program. Add the liquidity pool source filter too if you only want the canonical pool, since anyone can create other pools after graduation.

  6. Export CSV

    Click Export CSV at the top right of the tab. The file reflects your filters and, per Solscan's export guide, holds only the latest 1,000 records, even inside a filtered range. On a busy coin one hour can pass that, so split the window into chunks, export each one and combine them in a single sheet.

That 1,000-record limit is the one thing that trips people up. Solscan's export guide says the file returns only the latest 1,000 records, even inside a filtered range. On a busy coin, a single hour can pass that. Split the window into smaller chunks, export each one and paste them into one sheet, then check the first and last timestamps of each file so nothing falls through a gap between files.

Why does one trade equal one confirmed signature?

On Solana, every transaction is identified by its first signature. That signature is the transaction ID you see in Solscan links. A normal buy or sell from a wallet is one transaction, so for most rows one signature is one trade. Open any signature and the page shows its result. Only count those marked Success, because a failed transaction still lands in a block and still pays its network fee, but it doesn't move tokens or SOL through the pool.

One exception is worth knowing, though. A single transaction can hold several instructions, so aggregators and bundles sometimes pack more than one swap into one signature. In the DeFi Activities export those show up as several rows with the same signature. For a trade count, count rows. For a transaction count, count distinct signatures. Note which one you used when you compare with another tool, because each is fair and they give different numbers.

How do you count unique traders?

A trader is the address that signed the swap. On Solana, the first signer pays the fee and is normally the wallet doing the trade, and Solscan's swap rows show that account. To count unique traders, take the account column from your export, remove duplicates and count what's left. In most spreadsheets that's a single unique-count formula.

Don't confuse this with holders. The holder count is how many accounts hold a balance right now. Someone who bought and sold is a trader but not a holder. Someone who received tokens by transfer is a holder but never traded. Both numbers are useful. They just answer different questions. DexScreener calls its version makers, which our page on DexScreener trending explains next to volume.

If you want a sharper picture, sort the unique traders by how many rows each one has. A coin where a few addresses make most of the trades looks very different from one where hundreds of wallets each trade once or twice. Neither tells you who controls the wallets, but the distribution is a good first read on how spread out the activity is.

How do you total the SOL volume?

Every swap has two sides: the token and SOL. On the bonding curve the other side is native SOL. In a PumpSwap pool it's usually wrapped SOL, which is the same value in token form. In your export, find the column that holds the SOL or wrapped SOL amount for each row and sum it across all successful swaps. That total is the SOL volume for the window, buys and sells together.

Method only. Every number comes from your own export, not from us.
What you wantSpreadsheet stepNotes
Trade countCount rows after filtering to successful swapsRows, not signatures, if some signatures hold several swaps
Transaction countCount distinct signaturesMatches what most explorers call transactions
Unique tradersCount distinct account addressesSigners of the swaps, not holders
SOL volumeSum the SOL or wrapped SOL side of each rowBuys and sells both count
Buy and sell splitSum separately by directionSOL in to the curve or pool is a buy, SOL out is a sell

Should you total volume in SOL or dollars?

Total volume in SOL. Solscan does show a dollar value column for many rows, priced at the time of the trade, but the filter guide notes that value-based filtering only covers roughly the past year, so older periods need SOL anyway. Summing SOL is cleaner too. Prices move, but the SOL amount in a past trade never changes.

How do you tell a curve trade from a PumpSwap trade?

You tell a curve trade from a PumpSwap trade by the program it went through.

Open a signature and look at the instruction list. A bonding curve trade calls the Pump program, 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P, with a buy or sell instruction. A pool trade calls the PumpSwap program, pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA. The platform column in DeFi Activities usually tells you the same thing at a glance, but the program ID is the final word.

Timing helps too. Curve trading stops when the curve completes, and the next step is a migration transaction that creates the canonical pool, so every swap before that point is a curve trade. Every swap after it, in the canonical pool, is a pool trade. Our guide to Pump.fun graduation explains what completes the curve, and the bonding curve guide shows how each curve trade moves the price.

Watch for other pools. Why? After graduation anyone can create another pool for the same token, and trades there are real but separate. If you only care about the canonical pool, filter by the liquidity pool source as well as the platform. This also matters for creator rewards, since only the canonical pool pays the creator. Our page on Pump.fun creator rewards covers that side.

Why might your total differ from a chart?

Your total usually differs from a chart for six plain reasons: time windows, time zones, rows against signatures, pools included, price source and the export cap. Small differences are normal. Run through this list before deciding a number is wrong.

  1. Time windows. A 24-hour figure on a chart is a rolling window. Your export covers fixed timestamps.
  2. Time zones. Local time against UTC can shift a whole hour of trades in or out.
  3. Rows against signatures. One tool counts swaps, another counts transactions.
  4. Pools included. Some tools sum every pool for a token, others only the main pair.
  5. Price source. Dollar volume depends on which SOL price was used and when.
  6. Export cap. A window with more than 1,000 swaps needs several exports to be complete.

If your SOL total and trade count line up within these causes, the activity is what it looks like. Why check at all? So you don't have to trust a dashboard, ours included. Runs we place use 500 to 10,000 fresh wallets and send ordinary swaps, so the same steps apply to them as to any other trading. For the cost side of a run, see our volume bot price guide, with a minimum target of 100 SOL.

Quick answers

How do I verify volume on Solscan?

To verify volume on Solscan, open the coin's token page, go to DeFi Activities, set a date range, filter to token swaps and export the CSV. Sum the SOL side of every successful swap to get the volume, buys and sells together. Each CSV holds the latest 1,000 records, so a busy window needs several exports.

Does one Solana signature always equal one trade?

One Solana signature usually equals one trade, because a normal buy or sell is one transaction identified by its first signature. Aggregators and bundles can pack several swaps into one signature, which show up as several rows with the same signature in the DeFi Activities export. Count rows for trades and distinct signatures for transactions.

How do I count unique traders for a Pump.fun coin?

Count unique traders for a Pump.fun coin by taking the account column of successful swaps in your Solscan export, removing duplicates and counting the rest. These are the signing addresses, which differ from the holder count. The same 100 SOL of volume can come from 1 trader or 1,000, so the spread matters as much as the total.

Why does my Solscan export stop at 1,000 rows?

A Solscan export stops at 1,000 rows because, per Solscan's export guide, each CSV returns only the latest 1,000 records, even inside a filtered range. On a busy Pump.fun coin a single hour can pass that limit. Split long periods into shorter windows, export each one, then check the first and last timestamps so no gap sits between files.

How can I tell a bonding curve trade from a PumpSwap trade?

Tell a bonding curve trade from a PumpSwap trade by the program in the transaction. Curve trades go through the Pump program, 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P, and pool trades through the PumpSwap program, pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA. Every swap before the migration transaction is a curve trade, and the curve completes once 793,100,000 tokens are sold.

Should failed transactions count as volume?

Failed transactions shouldn't count as volume. Per the Solana docs on transactions, a failed transaction still lands in a block and pays its network fee, but it moves no tokens or SOL through the curve or pool. Count only rows with a Success status, and leave failures out of trade counts, transaction counts and the SOL total alike.

Every trade we place is on the ledger

Our runs send ordinary swaps you can audit on Solscan with the method on this page. Set the goal, see the flat price and pay by plain SOL transfer.

Mitchel Davis writes and maintains the Softatjeh guides and revises them whenever Pump.fun changes its curve, feed or PumpSwap rules. Found a stale number? Tell us at support@softatjeh.com.