ScanZX

Example report with invented data. DEMO Token is not a real token and this is not a real scan — it shows what a ScanZX report looks like. Run a real scan.

Observed-risk report · Ethereum · Example data

DEMO Token (DEMO)

HIGH OBSERVED RISK

0x7f3…a8b2 (example address) · Scanned 2 minutes ago (example) · Basic scan · methodology v1.1

Risk score (observed warning signs)72/100Higher = more red flags at scan time.
Confidence (data completeness)80/100Three checks could not run — each one lowers confidence, never risk.
ScanZX Slop Score (separate)68/100HIGH SLOP SIGNALS — hype/copycat naming heuristics. Not part of the risk score.

Top observed warnings

CRITICALHigh tax detected: Buy 25% / Sell 25%A quarter of every trade goes to the contract. Taxes this high are a strong warning sign at scan time.
HIGHMint function is not renouncedThe contract can create new tokens. Supply could be inflated at any moment.
HIGHTop 10 holders control 68.3%A small group of wallets could move the price sharply by selling.
HIGHLP lock not confirmedNo liquidity lock was observed. Liquidity could be withdrawn without notice.
MEDIUMOwner can change max transaction taxThe owner keeps permission to raise trading taxes after launch.

Multiple serious warning signs were observed in this example: live mint permission, unconfirmed liquidity lock, heavy holder concentration, and very high trading taxes.

Why this score? Category breakdown (example)
CategoryWeight (cap)Points countedObserved
Contract permissions2220Mint live, taxes changeable
Liquidity risk1814LP lock not confirmed
Holder concentration1412Top 10 hold 68.3%
Ownership / admin control1412Owner not renounced
Honeypot / tax / trading101025% buy and sell tax
Token age & lifecycle104Pair is 6 days old
Deployer history80Check unavailable — no points added, confidence reduced
External reputation40Check unavailable — no points added, confidence reduced

Points sum to the 72/100 risk score. Category totals are capped by the methodology weights — read the methodology.

Data sources and unavailable checks (example statuses)
Provider / checkStatus
On-chain read (RPC)Checked
DEXScreener market dataChecked
GoPlus security checksChecked
Etherscan source verificationNot configured
Holder clusteringUnavailable
Deployer historyPlaceholder — planned check

Checks that could not run: source verification, holder clustering, deployer history. Each one reduces the confidence score — unavailable data is never presented as a pass.

Share this example report

Real reports get a public link your whole community can open — no account needed.

Share to TelegramShare to XEmail

Example report only. ScanZX reports observed warning signs and never guarantees safety. Not financial advice.

Sample report (example data) | ScanZX