| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 19 Oct 2026 |
| Buy tax | 0% | Contract | 19 Oct 2026 |
| Sell tax | 0% | Contract | 19 Oct 2026 |
| Admin mint | Not present | Contract | 19 Oct 2026 |
| Transfers pausable | Not present | Contract | 19 Oct 2026 |
| Address blacklist | Not present | Contract | 19 Oct 2026 |
| Upgradeable proxy | No | Contract | 19 Oct 2026 |
| Source verified | Yes | Block explorer | 19 Oct 2026 |
| Top-10 holders | 46.5% | Holder distribution | 19 Oct 2026 |
| Liquidity locked | No | LP holders | 19 Oct 2026 |
| Holders | 43147 | Token contract | 19 Oct 2026 |
| Deployed by | 0x6468cc…e2eac2 |
| Current owner | None — ownership renounced |
| Holders | 43,147 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x27333b…d1f42c | 14.37% |
| #2 · contract | 0xd229b6…4da457 | 6.05% |
| #3 | 0xca9a3c…637401 | 4.23% |
| #4 | 0xb8210c…3520f1 | 4.11% |
| #5 | 0x571141…b07c0e | 3.47% |
This automated check on AKE (BSC) found an on-chain score of 16 out of 18, based on contract mechanics only, as detected on the date of the scan. In practice, this means a transfer simulation showed the token can be sold, and both buy and sell tax were read from the contract as 0%. No admin mint function was detected, meaning the contract owner does not appear to hold a coded ability to create new tokens at will. No pause function was detected, so the owner does not appear able to freeze all transfers, and no blacklist function was found, meaning there is no on-chain mechanism spotted that would let the owner block specific wallets from trading. The contract is also not upgradeable, so its core logic cannot be swapped out later by whoever deployed it. The two points worth sitting with are that the top 10 wallets hold 46.6% of supply, which is a meaningful concentration, and that liquidity is not locked, meaning whoever supplied the trading pool retains the ability to withdraw it, which is a mechanism separate from the token contract itself.
It's important to be clear about what this check does not cover. This is a purely mechanical read of the contract's code and the current state of the blockchain: it looks at functions, permissions, tax rates, and holder distribution as they exist right now. It says nothing about who is behind the project, whether the team's stated plans match their actual intentions, how the token is meant to be used, whether any legal or regulatory structure sits behind it, or whether the marketing around it is accurate. Source code being verified on the explorer means the code is readable and matches what's deployed, not that the code does what a reasonable holder would assume, nor that the people running it are acting in good faith.
Before putting any money in, it's worth looking at where the top 10 wallets came from and whether any are exchange or team addresses rather than independent holders, since concentration can matter differently depending on who holds it. Checking the liquidity pool directly on a site like BscScan to see who owns the LP tokens and whether they're locked elsewhere (even if not flagged by this tool) is also sensible. Beyond the contract, independently verifying the team's identity and history, reading any available audit reports in full rather than trusting a badge, and checking community channels for consistent, verifiable communication are all steps that sit outside what an automated contract scan can tell you.
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.