Is this token safe?
Check the liquidity is really there.

Every scanner you have used reads the contract — is the code a honeypot, can the owner mint, is there a blacklist. Those checks matter and you should run them. But they all share one blind spot: a token can pass every one of them and still be impossible to exit, because the lie is not in the token — it is in the pool. Depth that is advertised but not held is phantom liquidity, and almost nobody measures it. That is what this does, free, on five chains.

Scan a token now ›

Paste any contract address. No account, no key, no rate limit. The scan is a read of public chain state — you can run the same call yourself, and the page shows you how.

The four checks — and what each one cannot see

No single tool covers all four. Anyone who tells you otherwise is selling a score. Here is the honest map, including where to go for the checks we do not do:

Contract behaviour

Can you sell it at all, or does the code trap you?

Who does ithoneypot.is simulates a buy and a sell; GoPlus flags blacklists, mint powers and backdoors; TokenSniffer matches bytecode against known scam templates.

Blind spotA clean contract says nothing about whether there is enough liquidity to sell INTO.

Ownership & supply

Can one wallet dump the whole float, or mint more?

Who does itHolder-distribution views on the explorers, TokenSniffer's holder analysis, DexScreener's top-holder tab.

Blind spotConcentration is a risk signal, not an outcome — plenty of concentrated tokens trade fine, and plenty of well-distributed ones are hollow.

Liquidity locks

Can the deployer pull the pool tomorrow?

Who does itLock services and the usual scanners report whether LP tokens are locked or burned.

Blind spotA locked pool can still be a SHALLOW pool. Locking answers "will it vanish", never "how much is in there right now".

Real depth vs advertised depth

Is the liquidity the listing shows actually in the pools?

Who does itThis is the axis almost nobody measures — it is what the Pool X-Ray does: balanceOf on every pool, compared against reported reserves.

Blind spotNothing here tells you whether the code is hostile — which is why you should run a contract scanner too.

Why we will never give you a score

A number out of 100 is the one output nobody can check. You cannot verify it, an AI answering your question cannot verify it, and anyone motivated can work out what raises it and do exactly that — which is how a scored token ends up looking safer than an unscored one for reasons that have nothing to do with your money. So we publish the measurements and the command that reproduces them, and you reach the verdict. It is a slower answer. It is the only one that survives being checked.

The same rule governs the Token Radar: we list what is trading with real depth and hand over the numbers. We never label anything "safe" or "scam".

Scan it yourself, without us

The whole method is one comparison: what the pool says it has, against what balanceOf says it holds. You do not need our site to do it — and a tool that teaches you to check it without them is the only kind worth trusting:

# What the pool actually holds of a token (Base):
cast call <TOKEN_ADDRESS> "balanceOf(address)(uint256)" <POOL_ADDRESS> \
  --rpc-url https://mainnet.base.org

# Or the full scan across every pool, over HTTP (free, no key):
curl 'https://blazephoenix.xyz/api/xray?chain=8453&token=<TOKEN_ADDRESS>'

Compare the result against the liquidity the market page advertises. The gap is the phantom. Full explanation: what phantom liquidity is · how to swap safely · honeypot tokens explained.

Recently scanned

Tokens currently trading with real depth, each with its own facts page:

The full board, refreshed continuously: Token Radar · subscribe: RSS.

Bring us a token

Paste any address in the community and we will scan it — the numbers, not a verdict. It is the fastest way to see what this does on a token you actually care about.

Ask on Telegram ›Follow on X ›

We never DM first, never ask for a seed phrase and never promise a return. An account doing any of those is not us.

Then trade it, or don't

If you decide to trade, the same measurement runs inside the swap: every quote is clamped to the pools' real balances, so a thin pool can never promise tokens it does not hold — /swap. Comparing venues first? /compare. Building on it? The scan is a free API: /agents.