Ten checks. One card.
Paste a contract. Ten lines come back, each one green, red or grey, each one linked to the transaction behind it. No score, no verdict.
Live checks run in the bot today: t.me/NoPeek_Check_Bot. The card on this page shows example data until the API ships.
Crypto is risky. You can lose everything. Not financial advice.
- Contract powersPass:no mint · no pause
- Liquidity lockPass:locked 12m
- Launch botsFlag:84% in 5 min
- Insider clusterFlag:22% day one
- BurnsPass:real · 5.2%
- OwnerPass:renounced
- FeesUnknown:unknown
- Team supplyPass:3.0% · vesting
- Top-10 holdersPass:31%
- SourcePass:verified
EXAMPLE DATALive cards when the API ships.
What each line means
- 01
Contract powers
Reads the verified source and bytecode for functions that let someone change the token after launch: mint, pause, blacklist, tax changes, upgradeable proxy.
- green
- None of these functions exist, or none can be called by anyone.
- red
- At least one exists and can be called. The row names which ones.
- grey
- Source and bytecode could not be read, so the check did not run.
- 02
Liquidity lock
Finds the pool, the liquidity position and who holds it. Checks whether that holder can withdraw, and until when.
- green
- The position is locked or held by a contract with no withdraw path. The row shows how long.
- red
- The position is held by a wallet or contract that can withdraw it.
- grey
- No pool found yet, or the holder could not be classified.
- 03
Launch bots
Matches the first buyers against known bot wallets: wallets that bought into 20 or more launches within 60 seconds of launch.
- green
- Bots bought a small share of the supply in the first 5 minutes.
- red
- Bots bought a large share of the supply in the first 5 minutes. The row shows how much.
- grey
- Too few trades to measure.
- 04
Insider cluster
Follows the funding trail of early buyers: same funder, same gas source, same timing, supply split over many wallets.
- green
- No cluster linked to the deployer was found.
- red
- A cluster linked to the deployer holds supply. The row shows the share and the day it was bought.
- grey
- The trail could not be followed far enough to say.
- 05
Burns
Checks every claimed burn against the chain: transfers to the zero address or the dead address, with transaction links.
- green
- Burns happened on-chain and the numbers match.
- red
- A burn was claimed, but no matching transfers were found.
- grey
- No burn was claimed, or the scan has not covered the period yet.
- 06
Owner
Reads who owns the contract and what that owner can still do.
- green
- Ownership is renounced, or the owner has no powers left.
- red
- An owner exists and can still change something that affects holders.
- grey
- Ownership could not be read.
- 07
Fees
Reads the buy and sell tax and where collected fees go, following them to the final receiving wallet.
- green
- Tax is fixed and fees go where the project says.
- red
- Tax can be changed, or fees go somewhere the project does not mention.
- grey
- Fee routing could not be followed.
- 08
Team supply
Adds up what the deployer and linked wallets acquired: dev buy plus later buys, minus tokens sent to burn.
- green
- Team share is small or vesting, and visible on-chain.
- red
- Team share is large and free to sell.
- grey
- Team wallets could not be identified.
- 09
Top-10 holders
Adds up the share of supply held by the ten largest holders, excluding the pool and burn addresses.
- green
- Supply is spread out.
- red
- A few wallets hold most of the supply.
- grey
- Holder list not available yet.
- 10
Source
Checks whether the contract source is published and whether it compiles to the exact bytecode on-chain.
- green
- Source is published and matches the bytecode.
- red
- Source is missing or does not match the bytecode.
- grey
- Verifiers could not be reached.