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 | 2% | Contract | 18 Nov 2026 |
| Admin mint | Enabled | 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 |
| Top-10 holders | 78.9% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 2128 | Token contract | 18 Nov 2026 |
| Deployed by | 0x111119…025b46 |
| Current owner | 0x111119…025b46 |
| Holders | 2,128 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x2070b4…d25260 | 25.20% |
| #2 · contract | 0xf32fc5…996100 | 21.89% |
| #3 · contract | 0xd9b8fb…313b71 | 14.38% |
| #4 · Uniswap v4 pool · contract | 0x8366a3…e40951 | 6.05% |
| #5 | 0xec8c0a…f4ee3a | 3.29% |
This automated check scored SLVR 10 out of 18, and the individual findings describe what the contract's code allows, not what it promises. A transfer tax of up to 2% means a cut of each transaction can be redirected or kept on every trade, which reduces the amount a holder effectively receives on a sale. The admin mint function being enabled means whoever controls the owner address can create new SLVR tokens at will — this can dilute existing holders' share of supply without warning. Top-10 wallets holding 79.1% of supply indicates high concentration: a small number of addresses could move or sell large amounts at once, which can affect price sharply regardless of what the contract code says. No pause function, no blacklist function, and no upgradeable proxy were detected on the date of this check, meaning the owner does not currently appear to hold those particular levers — but this can change if the contract is redeployed or if related contracts exist elsewhere. The transfer simulation found the token sellable and no honeypot behaviour was detected at the time of testing. Liquidity not being locked means whoever supplied the trading pool can withdraw it, which can leave buyers unable to trade at a reasonable price even when the token itself is technically sellable.
It's worth being clear about what this check does not cover. It reads contract mechanics only — the code's functions and permissions, plus what's visible on-chain about holders and liquidity. It says nothing about who is behind the project, whether the team has a track record, how the tokenomics are intended to play out over time, whether there's any legal entity or jurisdiction backing it, or what the stated purpose of the token actually is. A contract can look mechanically unremarkable and still be attached to a project with no real activity behind it, and conversely a contract with concerning permissions isn't automatically evidence of bad intent.
Before putting money toward a token like this, it's worth looking at who holds the owner/admin address and whether it's a multisig or a single key, checking whether the project has published any information about team identity or roadmap, searching for independent commentary or audits beyond this automated scan, and watching how the liquidity pool and top holder wallets behave over a few days before deciding anything. Because liquidity isn't locked here, it's also reasonable to check whether the pool has grown, shrunk, or been withdrawn since this check was run, since that figure can change quickly.
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.