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 |
| Liquidity locked | 100% burned | LP holders | 18 Nov 2026 |
| Holders | 20 | Token contract | 18 Nov 2026 |
| Deployed by | 0xd73108…c23c3b |
| Holders | 20 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xd73108…c23c3b | 100.00% |
| #2 · Uniswap v4 pool · contract | 0x000000…e08a90 | 99.61% |
| #3 · contract | 0x3fc8d8…974e4c | 0.37% |
| #4 · contract | 0x000000…707555 | 0.09% |
| #5 · contract | 0x410144…0ea4a3 | 0.08% |
This automated check looked at the contract code for Macca (Macca the Gator) on Ethereum and did not detect several mechanisms that are commonly used to trap or drain holders. A transfer simulation showed the token could be sold at the time of the check, with no buy or sell tax applied. No admin minting function was found, meaning the contract owner does not appear to have a built-in way to create new tokens and dilute holders. No pause function was detected, so the owner does not appear able to freeze all transfers at will. No blacklist function was found, meaning there's no detected mechanism to block specific wallets from trading. The contract is not an upgradeable proxy, so its logic cannot be swapped out for different code after the fact without deploying an entirely new contract. The liquidity pool shows as 100% burned, which means those LP tokens have been sent to an address with no known private key, reducing the likelihood that liquidity can be pulled in one go. The contract source is verified on the block explorer, so the code matches what's publicly listed and could, in principle, be read line by line.
What this does not tell you is just as important. This is an automated read of contract mechanics only, run on the date of the check — it has not been reviewed by a person, and results can change if the contract is interacted with differently later or if related contracts (routers, auxiliary minting contracts, etc.) are updated. It says nothing about who is behind the project, whether the team has a history in other tokens, how tokens are distributed among wallets, whether there are off-chain promises or agreements, or whether marketing claims match reality. A clean contract read does not speak to tokenomics design, vesting schedules, or the intentions of whoever controls the deployer wallet and any remaining admin keys. With 274 holders, concentration risk is also worth examining directly rather than assumed from this score.
Before putting money in, it's worth looking at the holder distribution yourself on the block explorer to see what share the top wallets control, checking whether the deployer or team wallets hold a large portion of supply, searching for the project's social channels and history to see how long it's been active and how the team communicates, and confirming the liquidity lock or burn transaction directly on-chain rather than relying on a summary. None of this check constitutes investment advice, and a high score here reflects the absence of certain detected contract-level red flags on this date — not a judgement on the project as a whole.
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 12 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.