| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 2 Nov 2026 |
| Buy tax | 0% | Contract | 2 Nov 2026 |
| Sell tax | No data | Contract | 2 Nov 2026 |
| Admin mint | No data | Contract | 2 Nov 2026 |
| Transfers pausable | No data | Contract | 2 Nov 2026 |
| Address blacklist | No data | Contract | 2 Nov 2026 |
| Upgradeable proxy | No data | Contract | 2 Nov 2026 |
| Source verified | No | Block explorer | 2 Nov 2026 |
| Top-10 holders | 100% | Holder distribution | 2 Nov 2026 |
| Liquidity locked | No | LP holders | 2 Nov 2026 |
| Holders | 6 | Token contract | 2 Nov 2026 |
| Deployed by | 0xd1f3bb…e913dd |
| Holders | 6 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x2bb48b…f705ed | 52.01% |
| #2 | 0x867d7e…12f3f8 | 27.03% |
| #3 | 0x7ddb67…b0a945 | 20.49% |
| #4 · contract | 0xd1f3bb…e913dd | 0.47% |
| #5 · PancakeV3 · contract | 0x10da14…6f3299 | 0.00% |
This automated check simulated a sale of EMX on BscScan and found that selling is blocked by the contract — this pattern is known as a honeypot. In practice, this means that once tokens are bought, the contract's code prevents holders from converting them back out, regardless of price or market conditions. The top 10 holders — out of only 6 holders in total — control 100% of the supply, meaning a small number of wallets, potentially including the contract deployer, could hold nearly all tokens in circulation. The contract source code is not verified, so the exact logic behind these behaviours cannot be read directly; this check relied on bytecode simulation rather than human-readable code. Liquidity is also not locked, which means whoever controls the liquidity pool retains the ability to withdraw it at any time, separate from the selling restriction already detected. Because a token that cannot be sold automatically scores 0 on this check, no other signal — including the 0% buy tax — changes that outcome.
It's important to be clear about what this check does not do. It only reads contract mechanics as they exist on-chain at the time of the scan: whether transfers function, whether ownership controls are present, and how supply is distributed among wallets. It says nothing about the people behind the project, their intentions, any roadmap or marketing claims, the token's economic design, or whether any legal entity stands behind it. A contract can show no flags and still be part of a project with no real activity or plans, just as the presence of flags here reflects code behaviour, not a judgement about the people who deployed it.
Given that selling has been detected as blocked, there is no amount of purchase — including a small test buy — that would allow funds to be safely withdrawn once committed to this token; money that enters a contract with this behaviour stays there. If you want to understand this contract further without spending funds, you can review the raw bytecode or ask someone with Solidity experience to assess it, check the BscScan contract and transaction history for deployer activity, and look at whether the liquidity pool address and its transaction history show prior withdrawals. None of this changes the core finding already detected: as of this check, selling was not possible.
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.
Trading a meme coin? The meme coin check shows how much real money is in the pool and what you lose selling $1,000, who can pull that money out, who holds the supply and how it trades — ready within 3 minutes of payment, day or night.