Chain coverage · chain id 56

BNB Smart Chain token risk scanner

BNB Smart Chain has the longest history of high-volume token fraud of the five chains ScanZX covers, and the tooling reflects it: honeypot and trading-restriction detection is more developed here than anywhere else, because the pattern was industrialised here first. Cheap blocks plus a very large retail audience produced a deep catalogue of contract tricks that are now well documented and reasonably detectable.

Free account required — 5 basic scans per day, and no wallet connection at any point. ScanZX reports observed risk signals and data gaps; it never certifies a token. See how scoring works.

ScanZX activity on BNB Smart Chain

Insufficient dataCompleted scans
Insufficient dataScored high observed risk
Insufficient dataMost recent scan

Fewer than 25 completed BNB Smart Chain scans have been recorded on this instance, so no percentage is published. A figure drawn from a handful of scans would not be a statistic, and ScanZX does not print one it cannot support.

What runs on BNB Smart Chain, and what does not

Read live from this deployment’s configuration when the page was generated. A row says available only when a scan on BNB Smart Chain would actually perform that check — nothing here is a fixed badge.

CheckStatusWhat it means
On-chain contract readsAVAILABLEName, symbol, decimals, total supply, contract presence and owner address are read directly from BNB Smart Chain over public RPC. No API key is required, so this never degrades.
Source verification and proxy detectionNEEDS KEYThis deployment has no BscScan API key configured, so verified-source status and proxy detection are reported as unavailable in a scan and the confidence score is reduced accordingly. They are never guessed.
Market data (liquidity, volume, pair age)AVAILABLEIndexed pair data for BNB Smart Chain comes from DexScreener's public API. A token with no indexed pair returns no market data rather than a zero.
Security provider cross-checkAVAILABLEGoPlus Security is queried for BNB Smart Chain (chain id 56) on public rate-limited access. When it disagrees with on-chain or explorer data the conflict is recorded and confidence is lowered — the disagreement is shown, not resolved silently.
Sell simulation (honeypot path)AVAILABLEA sell path is simulated read-only against PancakeSwap V2 using BNB as the quote asset. This is an eth_call — no transaction is built, signed or sent, and no wallet is connected.
Holder concentrationNEEDS KEYHolder distribution needs BscScan access. Without a key this check is listed as unavailable in the report and lowers confidence.
Deployer historyAVAILABLEPrior tokens deployed by the same address that ScanZX itself previously scored as high risk. This is built from this system's own scan history on BNB Smart Chain, so it is thin for a chain or a deployer ScanZX has not seen much of — and it says so when it is.

Explorer data for this chain comes from BscScan (bscscan.com). Market data comes from DexScreener's indexed BNB Smart Chain pairs, dominated by PancakeSwap V2 and V3. Sell simulation runs against the PancakeSwap V2 router with WBNB as the quote asset, read-only.

Why BNB Smart Chain produces the risks it does

Low fees and high retail throughput make the honeypot economically rational on this chain in a way it is not on Ethereum: an attacker can absorb hundreds of failed launches because each one costs almost nothing, and a single successful one pays for all of them. That is why sell-side behaviour deserves more weight here than any other single signal, and why a failed sell simulation is treated as critical observed risk rather than as one factor among many.

Patterns that recur on BNB Smart Chain

Buys succeed, sells fail

The defining BNB Smart Chain pattern. Implementations range from an explicit blacklist, through a sell tax set to a confiscatory percentage, to trading gates that only the owner can open. ScanZX simulates a sell path read-only and treats a failure as critical — but a simulation that succeeds is not proof that a later sell will, because the owner may retain the ability to change the rules after you buy.

Mutable taxes

A contract that lets the owner change the buy or sell tax after launch can be honest at the moment you scan it and confiscatory an hour later. The presence of a tax-modification function matters more than the tax value the scan observes, and ScanZX reports both separately.

Deployers with a visible catalogue of failures

Because the same operators launch repeatedly on this chain, deployer history is genuinely informative here. ScanZX counts prior tokens by the same deployer that this system previously scored as high risk — an evidence-grade relationship, not guilt by transaction proximity. Three or more prior failures is the threshold that feeds the score.

These describe observed patterns, not any named project. A pattern appearing in a report is a reason to verify further — it is never proof of intent, and its absence is never clearance.

What to check first on BNB Smart Chain

  1. Sell simulation result — and whether the owner can still change trading rules afterwards.
  2. Whether buy and sell taxes are modifiable after launch.
  3. Blacklist, whitelist and pause functions, and who can call them.
  4. Deployer history: how many prior tokens from this address were previously scored high risk.

Each of these is scored as a separate factor with its own source and severity. The methodology page sets out the weights, the confidence model and how unavailable checks are handled.

BNB Smart Chain scanning questions

Does ScanZX support BNB Smart Chain?

Yes. BNB Smart Chain is one of the five chains that receive the deep EVM scan: on-chain contract reads, market data, a security-provider cross-check, sell-path simulation and deployer history. The table above shows which of those are configured on this deployment right now.

Can a scan prove a BNB Smart Chain token is safe?

No. ScanZX reports observed risk signals and the checks it could not run, alongside a confidence score. A low risk score with low confidence means little data was available — it is not clearance, and no result should be read as a recommendation to buy or sell.

Do I need to connect a wallet to scan a BNB Smart Chain token?

No. ScanZX never connects a wallet and never asks for a private key or a signature. Sell-path simulation is a read-only call against a router; no transaction is built, signed or sent.

What does ScanZX do when a check cannot run on BNB Smart Chain?

It reports the check as unavailable and lowers the report's confidence score. Missing data never makes a token look safer — that is the single rule the whole scoring model is built around.

ScanZX runs the deep EVM scan on five chains. Compare coverage:

Or start from the check you care about:

Cryptoassets are high risk and you could lose all money used to buy them. ScanZX reports observed warning signs and data gaps at scan time on BNB Smart Chain. It never guarantees that a token is safe, it is not financial advice, and it is not a recommendation to buy or sell anything. Always carry out your own further verification.