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 | No data | Transfer simulation | 15 Nov 2026 |
| Buy tax | No data | Contract | 15 Nov 2026 |
| Sell tax | No data | Contract | 15 Nov 2026 |
| Admin mint | Not present | Contract | 15 Nov 2026 |
| Transfers pausable | Not present | Contract | 15 Nov 2026 |
| Address blacklist | Enabled | Contract | 15 Nov 2026 |
| Upgradeable proxy | No | Contract | 15 Nov 2026 |
| Source verified | Yes | Block explorer | 15 Nov 2026 |
| Top-10 holders | 36.7% | Holder distribution | 15 Nov 2026 |
| Holders | 916 | Token contract | 15 Nov 2026 |
| Deployed by | 0x19d10f…7f6c64 |
| Current owner | 0x000000…00dead |
| Holders | 916 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x5c1fe7…0b5ba9 | 22.31% |
| #2 | 0xa22333…3423b8 | 2.20% |
| #3 | 0x8a5307…2ce870 | 1.77% |
| #4 | 0x1e1367…9b61df | 1.67% |
| #5 | 0x7fcb4c…57e48f | 1.61% |
This automated check of the MEWNB (Mewnbase) contract on Base returned a score of 8 out of 10, based solely on patterns found in the contract code as it existed on the date of the check. The most relevant finding is that the contract supports blacklisting: this means the function that lets the owner block a specific wallet address from transacting with the token was detected in the code. In practice, this gives whoever controls the contract's admin functions the ability to prevent a chosen holder from selling or transferring their tokens, regardless of that holder's intentions. No admin mint function and no transfer-pausing mechanism were detected, meaning the ability to create new tokens out of thin air or freeze all transfers network-wide was not found in the code as written. The contract is not an upgradeable proxy, so its logic cannot be silently swapped for different logic later without deploying a new contract. Source code is verified on the block explorer, which means the code is readable and matches what is deployed, but verification alone does not tell you what that code permits. Note also that whether the token can actually be sold, and what buy or sell tax applies, returned no data here — those are separate and important checks that were not completed in this scan.
Top-10 wallets hold 36.7% of the supply across 916 holders, which indicates a concentration of tokens that is worth weighing, since large holders moving their position can affect available liquidity and price regardless of any contract-level restrictions.
This check reads contract mechanics only. It says nothing about who is behind the project, whether the team is anonymous or doxxed, how the token's supply and incentives are structured, whether any legal entity stands behind it, or what the stated intentions of the owner are. A clean mechanical reading does not indicate trustworthy intent, and a flagged function does not by itself indicate malicious intent — it indicates a capability that exists in the code.
Before considering any transaction, it would be worth independently checking liquidity lock status and ownership renouncement on the explorer, reviewing recent holder and transaction activity for patterns, looking for independent audits or team disclosures, and confirming actual buy/sell behaviour and tax rates through a source built for that purpose, since this check did not return that data. Because this scan did not confirm whether the token is sellable, no test transaction of any size is a reliable way to find out — funds placed into a token that turns out to block sales remain in that token.
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.