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 | 17 Nov 2026 |
| Buy tax | 0% | Contract | 17 Nov 2026 |
| Sell tax | 0% | Contract | 17 Nov 2026 |
| Admin mint | Not present | Contract | 17 Nov 2026 |
| Transfers pausable | Not present | Contract | 17 Nov 2026 |
| Address blacklist | Not present | Contract | 17 Nov 2026 |
| Upgradeable proxy | No | Contract | 17 Nov 2026 |
| Source verified | Yes | Block explorer | 17 Nov 2026 |
| Liquidity locked | No | LP holders | 17 Nov 2026 |
| Holders | 62 | Token contract | 17 Nov 2026 |
| Deployed by | 0x0addde…1b79f2 |
| Holders | 62 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x0addde…1b79f2 | 100.00% |
| #2 · Uniswap v4 pool · contract | 0x000000…e08a90 | 81.93% |
| #3 · contract | 0xd38db3…c53349 | 4.21% |
| #4 | 0xc289b8…2bfc38 | 3.65% |
| #5 | 0x32fe4b…228543 | 2.42% |
This automated check scanned IMD's contract code and ran a simulated transfer on the date shown above, and it did not detect the mechanics that typically let a contract owner trap or drain holder funds. Selling worked in the simulation, and buy and sell tax were both read as 0%, meaning no hidden fee was detected on trades at the time of the check. No admin mint function was found, so nothing in the code currently lets the owner create new tokens out of thin air and dilute holders. No pause function was detected, meaning there's no built-in switch found that would let someone freeze transfers. No blacklist function was found, so the contract does not appear to let an address be singled out and blocked from trading. The contract is not an upgradeable proxy, which matters because upgradeable contracts can have their entire logic swapped out after launch, including logic nobody has reviewed yet; that risk was not found here. The source code is verified on the block explorer, meaning the code you can read is the code actually running, rather than a black box.
One flag stands out: liquidity is not locked. In practice, this means whoever controls the liquidity pool tokens could remove the paired liquidity from the pool at any time, which can sharply reduce the ability to sell at a reasonable price, even though no honeypot behaviour was detected in the transfer simulation itself. This is a separate risk from the contract code flags above, and it was not mitigated by anything else found in this scan.
It's worth being clear about what this check does not cover. It reads contract mechanics only — it says nothing about who is behind the project, how tokens are distributed among the team versus the public, whether there are vesting schedules or insider wallets, what the stated purpose of the token is, or whether any marketing claims match reality. A clean mechanical reading does not speak to intent, business viability, or legal status, and this was an automated process with no human review involved.
Before putting any money in, it's worth looking at how liquidity is currently controlled and by whom, checking the holder list for concentration in a small number of wallets, searching for the team's public track record and any audit beyond automated scanning, and reviewing the project's own documentation for how tokens were allocated and whether liquidity lock plans exist.
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.