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 | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | Not present | Contract | 18 Nov 2026 |
| Transfers pausable | Not present | Contract | 18 Nov 2026 |
| Address blacklist | Not present | Contract | 18 Nov 2026 |
| Upgradeable proxy | No | Contract | 18 Nov 2026 |
| Source verified | Yes | Block explorer | 18 Nov 2026 |
| Top-10 holders | 66.3% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 276 | Token contract | 18 Nov 2026 |
| Deployed by | 0xb007c1…a2546d |
| Holders | 276 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x238a35…d5e6c4 | 13.42% |
| #2 | 0x556088…848efc | 7.41% |
| #3 | 0x2523c5…4606d6 | 7.41% |
| #4 | 0x7a2a9b…8fa89b | 7.20% |
| #5 | 0xc4a388…ee6483 | 5.56% |
This automated check of ZSU on BSC found a score of 14 out of 18, with no honeypot behaviour detected: the simulation shows the token can be sold, and both buy and sell tax read at 0% on the date of the check. The contract also shows no admin mint function, no pause function on transfers, no blacklist mechanism, and it is not an upgradeable proxy — meaning that, based purely on the code, there is no built-in mechanism for the owner to mint new tokens out of thin air, freeze transfers, block specific wallets, or swap the contract logic after the fact. The source code is verified on the block explorer, which means the code you see is the code that's actually running, and it was readable enough to check these mechanics directly rather than relying on guesswork.
Two things stand out as not detected in the clean column. First, liquidity is not locked, which means whoever controls the liquidity pool tokens could, in principle, withdraw the paired liquidity at any time, reducing the ability of others to sell at a stable price — this is a separate risk from a honeypot but can produce a similar practical outcome for holders if it happens. Second, the top 10 holders control 66.3% of total supply, a concentration level that means a small number of wallets could move a large share of supply at once, which can affect price significantly regardless of what the contract code allows or restricts.
It's worth being clear about what this check does not cover. It reads contract mechanics only: tax rates, mint/pause/blacklist functions, proxy status, holder distribution, and liquidity lock status as they exist on-chain at the time of the check. It says nothing about who the team is, whether they have a track record, what the token is meant to do, how tokenomics are structured beyond raw holder percentages, or whether any marketing claims made elsewhere match reality. No human has reviewed this token or its project; the findings above come entirely from automated analysis of the contract and on-chain data.
Before putting money into this or any token, it's worth looking at the liquidity pool directly to see who holds the LP tokens and whether a lock exists outside what this check captured, checking whether the top holder wallets are exchange or team addresses versus unrelated individual holders, searching for the project's own documentation and any independent commentary about the team, and treating holder concentration and unlocked liquidity as factors that materially raise exposure even where no honeypot or hidden admin function was found.
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.