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 | ChainSift simulation | 12 Nov 2026 |
| Buy tax | 0% | Contract | 12 Nov 2026 |
| Sell tax | 0% | Contract | 12 Nov 2026 |
| Admin mint | No data | Contract | 12 Nov 2026 |
| Transfers pausable | No data | Contract | 12 Nov 2026 |
| Address blacklist | No data | Contract | 12 Nov 2026 |
| Upgradeable proxy | No data | Contract | 12 Nov 2026 |
| Source verified | No | Block explorer | 12 Nov 2026 |
| Top-10 holders | 51.8% | Holder distribution | 12 Nov 2026 |
| Liquidity locked | No | LP holders | 12 Nov 2026 |
| Holders | 1167 | Token contract | 12 Nov 2026 |
| Deployed by | 0x093fd0…40571c |
| Holders | 1,167 |
| Rank | Address | Share |
|---|---|---|
| #1 · UniswapV2 · contract | 0x29bac6…b804da | 12.73% |
| #2 | 0x596abf…6877e9 | 10.00% |
| #3 | 0x622b44…62bc84 | 5.63% |
| #4 | 0xba0a0a…38c3e5 | 4.39% |
| #5 · contract | 0x271c52…4edf1a | 4.00% |
This automated check gave Spicenet a low score of 2 out of 10 on Base, and it's worth understanding exactly why. A simulated transaction found the token sellable, with buy and sell tax both at 0%, so no honeypot behaviour was detected on the date of this check — meaning the automated test could buy and sell without getting stuck. However, the contract's source code is not verified on the block explorer, which means the check could only read raw bytecode rather than readable code. In practice, this means functions like minting new tokens, pausing transfers, blacklisting addresses, or upgrading the contract logic could not be confirmed either way — they show as "no data" because the automated system could not reliably inspect them, not because they were ruled out. If any of those functions exist, a contract owner could potentially mint additional supply, freeze trading, or block specific wallets from selling. Liquidity is also not locked, which means whoever controls the liquidity pool could remove it at any time, and the top 10 holders control 51.8% of supply, a concentration level that means a small number of wallets could move a large share of tokens at once.
It's important to be clear about what this check does not cover. This is an automated read of contract mechanics only — it does not assess who the team behind Spicenet is, their track record, how tokens are allocated or vested, whether there's a legal entity behind the project, or what their stated intentions are. No person has reviewed this contract or the project's background; the findings above come entirely from automated simulation and data pulled from the contract and block explorer.
Before putting money into this token, consider looking up the contract on a Base block explorer and checking whether the source code has since been verified, which would allow a clearer read of what the contract can and cannot do. It's also worth researching the team publicly, checking whether there's a published tokenomics or vesting schedule, and looking at the liquidity pool directly to see who holds the LP tokens and whether any lock exists outside what this check found. Given the unverified source and unlocked liquidity, treating the unknowns as live risks rather than assuming them resolved in your favour is a reasonable starting point.
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 10 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.