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 | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | No data | Contract | 18 Nov 2026 |
| Transfers pausable | No data | Contract | 18 Nov 2026 |
| Address blacklist | No data | Contract | 18 Nov 2026 |
| Upgradeable proxy | No data | Contract | 18 Nov 2026 |
| Source verified | No | Block explorer | 18 Nov 2026 |
| Top-10 holders | 28% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 143089 | Token contract | 18 Nov 2026 |
| Deployed by | 0x6dac63…95c20e |
| Holders | 143,089 |
| Rank | Address | Share |
|---|---|---|
| #1 · burned | 0x000000…00dead | 10.00% |
| #2 | 0x9e2934…451827 | 2.51% |
| #3 | 0x818ba9…013f52 | 2.45% |
| #4 | 0xf3e0d4…62b8fe | 2.34% |
| #5 | 0xf6b8b5…2b96ef | 2.07% |
This automated check gave mihao (ni hao cat) a score of 5 out of 10 on BSC. An automated simulation found the token sellable at the time of testing, with buy and sell tax both reported at 0%, and no honeypot behaviour was detected on that pass. However, several important contract functions — including admin mint rights, the ability to pause transfers, address blacklisting, and whether the contract sits behind an upgradeable proxy — were not reported by the data source and so could not be scored either way. In practice, this means the check cannot confirm whether the contract owner currently holds the power to mint new tokens, freeze transfers, block specific wallets from selling, or swap out the contract's logic entirely. If any of those functions exist and are active, the owner could use them to dilute holders, stop trading, or target individual addresses, even if the contract behaved normally in this test. The contract's source code is also not verified on the block explorer, meaning the check is reading raw bytecode rather than human-readable code, which limits how much can be independently confirmed about what the contract actually does. On top of this, liquidity is not locked, so whoever controls the liquidity pool could remove it at any time, and the top 10 holders control 28% of the supply, which is a concentration level that could allow coordinated selling to affect the price.
It's worth being clear about what this check does not do. It only reads contract mechanics and on-chain data as they exist today — it says nothing about who is behind the project, how the token's economics are designed to play out over time, whether any legal or regulatory structure applies, or what the team's actual intentions are. A contract can look technically unremarkable and still be part of a project with no real plan, poor communication, or an intent to abandon it later. None of that is visible from bytecode or holder tables.
Before putting money into this token, it would be worth looking at whether the project has a public, identifiable team, checking the liquidity pool directly on-chain to see who holds the LP tokens and whether they're locked or able to be withdrawn, searching for any independent audit of the verified source code (once available), and reviewing community channels and transaction history for patterns such as sudden large sells by top holders. Given that several key contract functions returned no data, it may also be worth waiting for or requesting source verification before forming a view on the contract's behaviour.
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.