| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — the sell tax takes the whole sale | ChainSift simulation | 21 Nov 2026 |
| Buy tax | 0% | Contract | 21 Nov 2026 |
| Sell tax | 100% | Contract | 21 Nov 2026 |
| Admin mint | No data | Contract | 21 Nov 2026 |
| Transfers pausable | No data | Contract | 21 Nov 2026 |
| Address blacklist | No data | Contract | 21 Nov 2026 |
| Upgradeable proxy | No data | Contract | 21 Nov 2026 |
| Source verified | No | Block explorer | 21 Nov 2026 |
| Top-10 holders | 99.7% | Holder distribution | 21 Nov 2026 |
| Liquidity locked | 100% until 1 Sept 2028 | LP holders · PinkLock02 | 21 Nov 2026 |
| Holders | 71290 | Token contract | 21 Nov 2026 |
| Deployed by | 0x2df49c…81350d |
| Holders | 71,290 |
| Rank | Address | Share |
|---|---|---|
| #1 · burned | 0x000000…00dead | 98.00% |
| #2 | 0xfe93a8…ae4f50 | 0.49% |
| #3 | 0x6e36b2…d97068 | 0.41% |
| #4 · contract | 0xe16ec4…6158b9 | 0.20% |
| #5 · PancakeV2 · contract | 0x49965b…f88ce2 | 0.15% |
This automated check returned a score of 0 out of 18 for this token, and the central reason is a honeypot flag: simulated sell transactions returned nothing, because the sell tax is set to take 100% of the transaction. In practice, this means that a wallet which buys this token has no simulated path to selling it back — the contract's own rules route the entire proceeds away from the seller. A transfer tax of up to 100% was also detected, which means the contract owner has configured the ability to confiscate some or all of a token's value simply by moving it, independent of any exchange. The contract source code is not verified on the block explorer, so this assessment is based on bytecode analysis only — nobody outside the deployer can easily read the exact logic governing these behaviours in plain language. Holder concentration is extremely high, with the top 10 wallets holding 99.7% of supply, meaning price action could be dominated by a very small number of addresses regardless of what the trading mechanics show.
It's worth being clear about what this check does not cover. This is an automated read of contract mechanics only — it simulates transactions, reads tax parameters, and inspects holder distribution. It does not assess who is behind the project, whether any team identity has been disclosed or verified, how tokens were allocated or vested, whether any legal entity stands behind the project, or what the stated intent of the deployer is. A locked liquidity pool, such as the 100% lock until September 2028 shown here, only restricts withdrawal of the paired liquidity — it says nothing about sell tax, transfer tax, or mint functions, and does not offset a confirmed honeypot finding.
Given that selling is blocked in simulation, this is not a case where a small test purchase would clarify anything — funds placed into a token with this sell-tax configuration do not have a demonstrated path back out, based on the data gathered. Anyone evaluating this token further, independent of this check, would want to look at the actual deployer wallet history, search for any public team identity or audit disclosures, review the token's stated purpose and whitepaper if one exists, and treat an unverified contract with a detected full-confiscation sell tax as a significant open question rather than something resolved by a locked liquidity pool or holder count alone.
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.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.