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 | 15 Nov 2026 |
| Buy tax | 0% | Contract | 15 Nov 2026 |
| Sell tax | 0% | Contract | 15 Nov 2026 |
| Admin mint | Not present | Contract | 15 Nov 2026 |
| Transfers pausable | Not present | Contract | 15 Nov 2026 |
| Address blacklist | Not present | Contract | 15 Nov 2026 |
| Upgradeable proxy | No | Contract | 15 Nov 2026 |
| Source verified | Yes | Block explorer | 15 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 15 Nov 2026 |
| Holders | 1254 | Token contract | 15 Nov 2026 |
| Deployed by | 0x36aaad…e7577f |
| Holders | 1,254 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x36aaad…e7577f | 100.00% |
| #2 · Uniswap v4 pool · contract | 0x000000…e08a90 | 24.36% |
| #3 | 0x0e8f8a…0382fd | 1.26% |
| #4 | 0xe5495c…9dd6b4 | 0.91% |
| #5 | 0x394593…6427e5 | 0.88% |
This automated check of AudaCity on Ethereum returned a score of 12 out of 12, meaning that, as of the date of the check, none of the contract mechanics scanned for were detected as present. In practical terms: a simulated transfer went through, so the token was sellable at the time of testing. Buy and sell tax were both read from the contract as 0%, meaning no hidden fee was found reducing a trade. No admin mint function was present, which means the contract owner does not appear to hold a coded ability to create new tokens and dilute holders. Transfers were not found to be pausable, so the owner does not appear able to freeze trading at will. No address blacklist function was detected, meaning the owner does not appear to be able to block specific wallets from selling. The contract is not an upgradeable proxy, which means its logic cannot be swapped out later by the deployer without deploying an entirely new contract. The source code is verified on the block explorer, so what's publicly listed can be matched against what is actually deployed. Liquidity is recorded as 100% burned, meaning the LP tokens behind the trading pair have been sent to a dead address rather than held by a wallet that could withdraw the paired liquidity.
It's worth being clear about what this check does not cover. It reads contract code and on-chain state only — it does not evaluate who the team behind the project is, whether they have a history in other projects, how tokens are distributed among the 673 holders currently on record, what the actual purpose or roadmap of the project is, or whether any legal or regulatory structure applies to it. A contract can score well on mechanics like this one and still carry risk from concentrated holdings, undisclosed team allocations, marketing practices, or simply the project failing to develop as described. None of that is assessed by scanning contract code, because none of it lives in the contract.
Before putting money in, it's worth looking at the holder distribution directly on the block explorer to see whether a small number of wallets hold a large share of supply, checking whether the liquidity lock or burn can be independently verified on a tracker rather than taken from a single source, looking for any public information about the team or audit history, and reviewing the project's own communications for consistency over time. None of this replaces independent research, and none of the findings above should be read as a statement that the token is safe to buy.
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.