Analysing this token. The results appear here when the scan finishes.
Market Cap
Total Liquidity
Total Supply
Tax
Creator
Owner
Decompiling the contract and running static analysis
A token we have not seen before can take a few minutes. The results appear here when it finishes.
Analysing this token. The results appear here when the scan finishes.
Market Cap
Total Liquidity
Total Supply
Tax
Creator
Owner
Decompiling the contract and running static analysis
A token we have not seen before can take a few minutes. The results appear here when it finishes.
Market Cap
$4.8K
Total Liquidity
$12.97
Total Supply
1.00B
Tax (send / receive)
0% / 0%
Creator
Owner
RENAME (RENAME) on Base shows high-risk patterns in Tok{In}'s bytecode analysis. No trade was simulated because every pool holds less than $100 of liquidity (the largest holds $12.97), so nobody has checked whether this token can be sold. That is not a clean bill of health. Tok{In} found 5 risk flags (Funds Can Be Drained, Allowance Bypass, Pause Mechanism). 1 finding is neutralized (Pause Modifiable: owner renounced). Market cap $4.8K, liquidity $12.97, last scanned 15h ago. This is not financial advice: verdicts can change, so re-scan before trading.
| Finding | Status |
|---|---|
| Danger | |
| Danger | |
| Warning | |
| Warning | |
| Warning | |
| Neutralized |
10 of 23 checks passed, 7 undetermined. Last scanned 15h ago. Powered by Dedaub's Decompiler.
5 flags
Somebody other than the holder can move this token out of a wallet. Whoever holds that privilege can empty any wallet holding it, with nothing signed and no warning. A standard ERC-20 token cannot do this, and no holder action prevents it — selling out is the only defence.
Tokens can leave a wallet through an approval-based transfer the holder never granted. Whoever holds that privilege can drain any wallet that holds this token, with no approval ever signed. A standard ERC-20 token cannot do this. This is the mechanism behind Funds Can Be Drained.
The token has code that could pause trading. May be true even if the contract's current state doesn't allow re-enabling the pause.
The transfer function's behavior depends on a storage variable, which could be used to block or modify transfers.
The transferFrom function's behavior depends on a storage variable, which could be used to block or modify delegated transfers.
1 noted
Whether verified source exists for this contract's exact code. The match is on the code itself rather than the address, so source from an identical deployment counts and this address can still show as unverified on the block explorer. The findings above do not depend on it: Tok{In} reads the deployed bytecode directly.
Neutralized
The code has these findings, but the chain state has switched them off. Each one counts as passed.
The owner has renounced ownership. So the owner can no longer change this setting.
These checks returned no answer for this contract. Treat them as unanswered rather than clear.
| Pool | Buy / sell | Liquidity | |
|---|---|---|---|
UniV4 | fee -- / -- | $12.97100.00% of total |
