How Do You Check Token Risk on BscScan? Contract Permissions, Holder Distribution and Transaction Records

To judge the risk of a BEP20 token on BscScan, check four layers one by one: contract verification and permissions, Holders distribution, liquidity locking, and Transfers plus DEX trade records. This guide gives a six-step process, a risk-signal table and a checklist to use before buying.

Published on 2026-11-01 · About 36 min read · On-Chain Data Analysis

How do you tell whether a BEP20 token is risky on BscScan? The core method is to paste the token contract address into BscScan and then check, in order, whether the contract is verified, how much power the owner holds, whether the Holders list is overly concentrated and whether liquidity is locked, and finally to confirm with Transfers and DEX trade records that selling works normally. Before moving funds onto the BSC network, you can set up your account and security settings on the Binance Official Site and confirm the BEP20 deposit network in the Official Binance App; iPhone users can follow the site's iOS installation tutorial. BscScan only displays public on-chain data and cannot guarantee that any token is "absolutely safe", so the results of a check can only reduce the odds of stepping on a trap.

The overall approach to checking token risk on BscScan

Token risk can be split into three layers: whether the contract itself can be abused, whether the supply is concentrated in a few addresses, and whether real trades can be sold without trouble. The three layers map to three groups of pages on BscScan, and a conclusion that is cross-checked across them is far more reliable than one based on a single indicator.

Layer Where it lives on BscScan Main question answered
Contract layer Contract tab (Code, Read Contract, Write Contract) Is the source code public, and can the owner mint, blacklist, change tax rates or pause trading
Holder layer Holders tab and Analytics What share do the top addresses hold, and are they mostly controlled by the project team
Trade layer Transfers tab, BEP-20 Token Txns on an address page, transaction detail page Do both buys and sells succeed, and are there abnormal bulk transfers out

None of the three layers can be skipped. A contract with clean source code can still be dumped on if more than 80% of the supply sits in a single address, and a holder list that looks spread out can still hide a blacklist function that blocks selling.

What to prepare before checking

The most important preparation is obtaining the correct contract address and confirming that the browser is on the official BscScan domain. On BSC, a popular token can have many counterfeit contracts. The name, symbol and logo can all be copied, but the contract address cannot.

Sources of a contract address, ranked roughly from most to least trustworthy:

Source Trust level Notes
Contract address published on the project's official website and official social accounts Fairly high First confirm that the website and accounts themselves are genuine
Contract field on data sites such as CoinMarketCap and CoinGecko Fairly high Use the BNB Chain contract shown on the listing page and cross-check it with the official website
Contract information on a coin detail or deposit page in the Binance app Fairly high Follow what the Binance app currently displays
Addresses forwarded in group chats, private messages or tweet replies Low The main distribution channel for phishing and counterfeit tokens; should not be trusted directly

When you open the browser, type bscscan.com yourself or use a bookmark you saved earlier. Do not click a "BscScan link" sent by a stranger, because it may lead to a look-alike page. BscScan is a third-party explorer and a different product from the Binance exchange; its features follow whatever BscScan currently shows.

The six-step checking process

A complete BscScan token risk check has six steps, starting with confirming identity and ending with verifying real trades. Each step has a clear focus, explained below in order.

Step 1: Confirm the contract address and basic token information

The goal of the first step is to confirm that the page you are viewing is the genuine contract of the target token. Paste the contract address into the BscScan search box, open the Token page, and check the token name, symbol, Decimals, Total Supply and the number of Holders in the Overview area.

Watch for three things here. If a red or yellow warning label from BscScan appears at the top of the page, read its content first. Total Supply must match the figure published by the project. The Creator address and the creation transaction (Txn Hash) in the Contract area can be opened to see who deployed the contract and when.

A token that was deployed only a short time ago, has very few Holders and still claims to be "already booming" calls for extra caution. Another trait of counterfeit tokens is that several contracts exist under the same symbol, so the one published by the official project should be the reference.

Step 2: Check whether the contract is verified

A token whose contract source code is not verified carries clearly higher risk than one whose code is verified. Open the Contract tab. A verified contract displays "Contract Source Code Verified" together with the full Solidity source; an unverified contract only shows a string of bytecode, so its logic cannot be judged.

Verified only means that "the on-chain bytecode matches the published source code". It does not mean the contract has no backdoor. This has the same meaning as the Verified Contract badge on Etherscan.

An unverified contract is sometimes just something the project team has not yet submitted, but in many cases the code is hidden on purpose. Ordinary users cannot audit bytecode, so the sensible stance toward an unverified contract is to avoid it rather than guess.

Step 3: Read the owner and key permissions in the contract

The focus of a permission check is whether the owner can change the rules. In the Contract tab, switch to Read Contract and look at read-only functions such as owner, decimals and totalSupply. Then browse the function names in Code and note which ones only the owner can call.

The table below lists common high-risk functions and what they mean. Function names differ from project to project.

Function or feature Meaning Risk description
mint The owner can issue more tokens Supply can be diluted without limit, damaging the value of holdings
blacklist / setBlacklist The owner can blacklist specific addresses A blacklisted address cannot transfer or sell
setFee / setTax The owner can adjust buy and sell tax rates When the tax is set extremely high, selling returns almost nothing
pause / setTradingEnabled The owner can pause or shut down trading Transfers can be frozen for everyone at any time
Upgradeable Proxy contract The logic contract can be replaced The code you see today may be swapped for a different set later
renounceOwnership already executed Ownership moved to the zero address or a dead address Permission-related risk is lower, but other entry points still need checking

If the owner function in Read Contract returns 0x000000000000000000000000000000000000dEaD or an all-zero address, ownership has been renounced. If it returns an ordinary external address, that address holds the permissions and its transaction history should be opened for a closer look.

Step 4: Analyze the Holders distribution

Holder distribution shows whether the supply is controlled by a few addresses. Open the Holders tab on the Token page. The list is sorted from the largest balance to the smallest and shows each share, while the Analytics tab presents the distribution as charts.

When reading the Holders list, first exclude several kinds of normal large addresses: liquidity pool contracts (for example the pair contract on PancakeSwap), dead addresses, known exchange hot wallets and lock-up contracts. A high share for these addresses is usually normal. Only after excluding them can the real individual holdings be seen.

Holding pattern Possible meaning How to respond
The liquidity pool contract holds a large share Most tokens sit in the pool, a common structure Combine with step 5 to check whether the LP tokens are locked
The top individual addresses together hold a large share Concentrated supply with a possibility of bulk selling Open these addresses and check whether they share a source with the creator
Several addresses hold almost identical amounts May be split wallets controlled by one person Check whether their funds came from the same address
Few Holders in total and no growth over a long time Few genuine participants Treat as a sign of weak liquidity and attention

There is no universal standard for how large a share counts as "overly concentrated". It depends on the type of project, so a fixed number should not be applied mechanically.

Step 5: Check liquidity and LP locking

Whether liquidity is locked determines whether the project team can withdraw the entire pool at once. After liquidity is added on a DEX such as PancakeSwap, the project team receives LP tokens. If the LP tokens stay in the team's wallet, the team can remove liquidity at any time, an action commonly called a "rug pull".

To check, first find the pair contract address on the Token page (it usually appears near the top of Holders), open that pair contract and look at the Holders distribution of its LP token. If the LP tokens are concentrated in a dead address (burned) or a third-party lock-up contract, and the lock lasts long enough, the risk is relatively lower. If they sit in one ordinary external address, that is a high-risk signal.

The expiry date of a lock must be verified on the page of the corresponding lock platform, and the data follows what that platform displays.

Step 6: Verify that selling works using Transfers and trade records

Trade records are the most direct evidence of whether a token can be sold. In the Transfers tab on the Token page, every transfer is listed. Open an address and switch to BEP-20 Token Txns to see the complete buy and sell history of that address for this token.

Look at three kinds of patterns. First, are there many addresses that only bought and almost never sold, which may indicate a honeypot that cannot be sold? Second, do sell transactions often show a Fail status on the detail page, and what is the reason given? Third, have addresses linked to the project team recently moved large amounts of tokens into exchanges or DEX pools?

On a transaction detail page, the Status field shows Success or Fail, and the Tokens Transferred area shows the amount that was actually moved. If the amount received after a sale is far lower than expected, the contract probably applies a high sell tax.

Table of common risk signals

Risk should be judged by putting several signals together, because a single signal is not enough for a conclusion. The table below collects the signals that appear most often across the six steps, with suggested handling.

Risk signal Where it appears Risk level Suggested handling
Contract source code not verified Contract tab High Avoid taking part, since the logic cannot be audited
Owner is an ordinary address and keeps mint or blacklist Read Contract and Code High Decide whether being diluted or blacklisted is acceptable
Contract is a Proxy and upgrade rights are held by a single address Proxy notice on the Contract page Medium to high Check whether the admin is a multisig or has a timelock
LP tokens sit in the project team's personal wallet Holders of the pair contract High Pool withdrawal risk, so treat with caution
Top ten individual addresses together hold a large share Holders tab Medium to high Check whether they share a source and assess bulk-selling risk
Many sell transactions Fail or the amount received is abnormal Transaction detail page High A honeypot mechanism may exist, so stop operating
Recently deployed and Holders growing unusually fast Token page and Transfers Medium Possibly inflated numbers, observe for a while

The "risk level" in the table is a general rule of thumb and is not investment advice. Even when none of the signals appear, the token price can still swing sharply for market reasons.

Risk warnings and security notes

A BscScan check can only identify risks that are visible on-chain; it cannot cover a project team's intent or market volatility. Keep the following points in mind.

  • Do not test whether a token can be sold with a large amount of money, and never click an approval on an unfamiliar website. After approval, a contract may gain the right to move your tokens away.
  • Labels, scores and third-party data on BscScan pages come from different sources and may lag or be wrong, so cross-check them with several sources.
  • Any recommendation that promises "guaranteed profit" or "insider information" should be treated as high-risk information, because BscScan cannot verify whether a promise is true.
  • Cryptocurrency trading involves sharp price swings and the risk of losing principal, so assess your own tolerance before investing.
  • Users in mainland China should pay attention to the laws and regulations on crypto-related activity in their region and judge for themselves whether on-chain operations are compliant. This article only explains how to use the explorer and is not investment advice.

BscScan is an independent third-party blockchain explorer, and this site is likewise an independent third-party tutorial site with no affiliation to BscScan or to Binance.

Checklist

For every token you check, work through the list below item by item.

  • [ ] The contract address comes from the official website or a trusted data site and matches the BscScan page
  • [ ] The current domain is bscscan.com and was not reached through an unfamiliar link
  • [ ] The Contract tab shows the source code as verified
  • [ ] Permissions such as owner, mint, blacklist and tax rates have been checked in Read Contract and Code
  • [ ] It is confirmed whether the contract is a Proxy and who holds the upgrade rights
  • [ ] The top Holders were analyzed after excluding liquidity pools, dead addresses and exchange addresses
  • [ ] It is checked whether the LP tokens of the pair contract are locked or burned
  • [ ] Transfers and buy-sell records were reviewed, and normal sell transactions exist
  • [ ] Your own risk tolerance has been assessed and only money you can afford to lose is used

FAQ

Q: Can BscScan tell me directly whether a token is a scam? A: No. BscScan shows raw on-chain data and some community labels. To judge risk, you need to check the contract, the holders and the trades yourself and cross-check with other sources.

Q: If the contract shows as verified, does that mean the token is safe? A: No. Verified only means the published source matches the on-chain bytecode. The source may still keep permissions to mint, blacklist or change tax rates, so Code and Read Contract still need to be checked.

Q: What is a honeypot token, and how can you spot one on BscScan? A: A honeypot is a token that can be bought but is hard or impossible to sell. On the address page, look at BEP-20 Token Txns to see whether there are almost only buy records and whether sell transactions often show Fail, then combine that with the blacklist and tax functions in the contract.

Q: Is a high share for the top Holders always a problem? A: Not necessarily. High shares for liquidity pool contracts, dead addresses, exchange hot wallets and lock-up contracts are common. Exclude them first, then see whether the remaining individual addresses are concentrated and share a source.

Q: How can I confirm whether liquidity is locked? A: Find the token's pair contract and look at the Holders distribution of its LP token. If the LP tokens are mainly in a dead address or a third-party lock-up contract and the lock runs for a long time, the risk is relatively lower. If they are in an ordinary personal address, there is a pool withdrawal risk.

Q: Can the data on BscScan be inaccurate? A: On-chain transaction records themselves cannot be altered, but the calculation method and refresh speed of labels, scores and holding percentages may differ, and pages can lag. Rely on the raw on-chain transactions and compare several sources.

Q: Can I verify a token contract directly inside the Binance app? A: The deposit page and coin detail pages in the Binance app show the available networks and some contract information, and the exact content follows what the Binance app currently displays. For deeper on-chain checks, you still need to return to BscScan to view the contract and transactions.

Summary

The most reliable way to judge token risk on BscScan is to check contract permissions, holder distribution, liquidity locking and real trade records in sequence. A single signal only offers a lead, and indicators gain value when they confirm one another.

After the check, if you need to deposit through the BEP20 network or buy major coins, you can sign in through the Binance Official Site and confirm the network selection in the Official Binance App, following the information Binance currently displays. On-chain checking is an aid and cannot replace independent judgment about the project and your own risk tolerance.