Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 15 Nov 2026 |
| Buy tax | 0% | Contract | 15 Nov 2026 |
| Sell tax | 0% | Contract | 15 Nov 2026 |
| Admin mint | No data | Contract | 15 Nov 2026 |
| Transfers pausable | No data | Contract | 15 Nov 2026 |
| Address blacklist | No data | Contract | 15 Nov 2026 |
| Upgradeable proxy | No data | Contract | 15 Nov 2026 |
| Source verified | No | Block explorer | 15 Nov 2026 |
| Top-10 holders | 6.1% | Holder distribution | 15 Nov 2026 |
| Liquidity locked | No | LP holders | 15 Nov 2026 |
| Holders | 343 | Token contract | 15 Nov 2026 |
| Deployed by | 0x4a8455…a2df51 |
| Holders | 343 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xc50062…653696 | 0.88% |
| #2 | 0x3e283b…2a4b64 | 0.62% |
| #3 | 0xa72963…27065f | 0.61% |
| #4 · contract | 0x4a8455…a2df51 | 0.60% |
| #5 | 0x6398fa…5ec4b0 | 0.56% |
This automated check on BASEAI returned a score of 6 out of 10 on BNB Chain. A simulated sell transaction completed successfully, so no honeypot behaviour was detected at the time of the check, and the buy and sell tax both read 0%, meaning no fee was taken on either side of that test trade. Top-10 wallets hold 6.1% of the supply, which is on the lower end and not an immediate concentration flag by itself. However, several important contract mechanics could not be read at all: whether the owner can mint new tokens, pause transfers, blacklist addresses, or swap the contract logic via an upgradeable proxy all came back as "no data." That is not the same as those functions being absent — it means this check could not confirm either way, and any of them, if present, would let the contract owner alter supply, freeze specific wallets, or change how the token behaves after you hold it. On top of that, the contract source code is not verified on the block explorer, so the check is reading raw bytecode rather than human-readable logic, which limits how much confidence can be placed in any mechanical reading. Liquidity is also not locked, meaning whoever controls the liquidity pool could withdraw it at any time, which can make a token difficult or impossible to sell even if the contract itself permits selling.
It's worth being clear about what this check does not cover. It only reads contract mechanics and on-chain data as they existed at the time of the scan. It says nothing about who is behind the project, their track record, the token's economic design, whether there's a working product, or any legal status. A contract can score well on mechanics while still being tied to a team with no history, misleading marketing, or a tokenomics structure that concentrates value unfairly over time. None of that intent or quality is assessed here.
Before considering any action, it would be worth checking the contract on the block explorer directly to see if source code has since been verified, looking at the liquidity pool itself to see who holds the LP tokens and whether a lock exists on a locking service, reviewing the project's own communications and any audit reports from third parties, and searching independently for information about the team and the token's history on-chain. Given the unverified source and unlocked liquidity, treating the unknowns here as unresolved rather than assuming them to be benign would be a reasonable starting point.
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 10 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.