| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 25 Oct 2026 |
| Buy tax | 0% | Contract | 25 Oct 2026 |
| Sell tax | No data | Contract | 25 Oct 2026 |
| Admin mint | No data | Contract | 25 Oct 2026 |
| Transfers pausable | No data | Contract | 25 Oct 2026 |
| Address blacklist | Enabled | Contract bytecode | 25 Oct 2026 |
| Upgradeable proxy | No data | Contract | 25 Oct 2026 |
| Source verified | No | Block explorer | 25 Oct 2026 |
| Top-10 holders | 100% | Holder distribution | 25 Oct 2026 |
| Liquidity locked | No | LP holders | 25 Oct 2026 |
| Holders | 408 | Token contract | 25 Oct 2026 |
| Deployed by | 0x0faa90…a95d6d |
| Holders | 408 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x0faa90…a95d6d | 99.99% |
| #2 | 0xa387e3…147c32 | 0.00% |
| #3 | 0x035fcb…dd715e | 0.00% |
| #4 | 0x13c530…7efcbd | 0.00% |
| #5 | 0x1c1b1f…31958f | 0.00% |
This automated check found that DFCN's contract blocks selling: in a simulated transaction, tokens could be bought but not sold back. In practice, this means anyone holding DFCN who puts money into it would not be able to convert those tokens back out through normal means, regardless of price movement or market conditions. The contract also supports blacklisting, which would let whoever controls it block specific wallet addresses from transacting at all. On top of this, the top ten holders — which may include the contract owner or associated wallets — control the entire token supply between them, and the liquidity behind the token is not locked, meaning it could be withdrawn from the trading pool at any time. The contract's source code is also unverified, so its exact mechanics are not visible — this check has read the compiled bytecode only, not human-readable code, which limits how much can be confirmed either way. Because selling is blocked, this token scores 0 out of 18 on this check, regardless of how the other individual signals read.
It's worth being clear about what this check does and doesn't cover. This is an automated read of the contract's mechanical behaviour — things like whether a sell function works, whether holders are concentrated, whether liquidity is locked, whether the code is verified. No person has reviewed this token, and nothing here speaks to the team behind DFCN, their intentions, the project's actual tokenomics or roadmap, or any legal or regulatory status. A contract can show no technical red flags and still involve people acting in bad faith, and conversely, unusual contract code does not always mean malicious intent. This check simply cannot see any of that.
Given that selling is currently blocked, there's no safe way to "test" this with a small purchase — if a contract won't let tokens be sold, that applies however much is put in, so money placed into it would remain stuck regardless of amount. Beyond this check, it would be worth looking at the project's own communications and any independent audits, checking the block explorer directly for the contract owner's transaction history and recent activity, and searching for other reports or discussion of this specific contract address from other users or researchers before forming any view on it.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 18 points out of 100.
The other 82 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.