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 | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | 0% | Contract | 22 Nov 2026 |
| Admin mint | Not present | Contract | 22 Nov 2026 |
| Transfers pausable | Not present | Contract | 22 Nov 2026 |
| Address blacklist | Not present | Contract | 22 Nov 2026 |
| Upgradeable proxy | No | Contract | 22 Nov 2026 |
| Source verified | Yes | Block explorer | 22 Nov 2026 |
| Top-10 holders | 89% | Holder distribution | 22 Nov 2026 |
| Liquidity locked | No | LP holders | 22 Nov 2026 |
| Holders | 280 | Token contract | 22 Nov 2026 |
| Deployed by | 0x3098db…748603 |
| Holders | 280 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x3098db…748603 | 49.90% |
| #2 · Uniswap v4 pool · contract | 0x8366a3…e40951 | 12.72% |
| #3 · contract | 0xde56b6…f1898c | 11.67% |
| #4 · contract | 0xd40851…a2383f | 4.87% |
| #5 | 0x62f7e2…7dbae4 | 3.05% |
This automated check scanned CLAUDIA's contract code and current on-chain data, and scored it 13 out of 18. A transfer simulation found the token sellable, with no buy or sell tax detected, and no admin mint function, pausable transfers, blacklist capability, or upgradeable proxy pattern were found in the contract as published. In practical terms, this means that on the date of the check, the contract owner was not seen to have built-in mechanisms to block sales, freeze specific wallets, mint new tokens out of thin air, or silently swap in new contract logic. The contract source is also verified on the block explorer, meaning the code you can read is the code actually running, which supports the other findings but doesn't change what they say.
Two things pull the score down and deserve attention. First, the top 10 holders control 89% of the supply, meaning a small number of wallets can sell at any time and affect the price significantly, independent of anything the contract code does. Second, liquidity is not locked, meaning whoever supplied the trading pool can withdraw it whenever they choose, which can leave buyers holding a token with little or no functioning market to sell into. Neither of these is a coding flag in the usual sense, but both describe a concentration of power and of exit options sitting outside the average holder's control.
What this check does not tell you matters just as much as what it does. It reads contract mechanics and current holder/liquidity data only, as of the date of the check. It says nothing about who is behind the project, whether the team is anonymous, what the tokenomics or vesting schedule look like, whether there's a whitepaper or roadmap worth anything, or whether any marketing claims are accurate. A clean contract scan does not speak to intent, and a contract with no technical red flags can still be part of a project where the human decisions around it carry risk. Source verification and an absence of flags describe the code, not the people running it.
Before considering any transaction, it would be reasonable to look at the liquidity pool directly to see who holds the LP tokens and whether a lock exists outside what's shown here, to check whether the top holder wallets are known entities (exchanges, team, or treasury) or unexplained individual addresses, to search for any audit or community discussion of the project, and to re-run a check like this closer to the time of any decision, since contract permissions, holder concentration, and liquidity conditions can all change.
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.