| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | No data | Contract | 22 Nov 2026 |
| Admin mint | No data | Contract | 22 Nov 2026 |
| Transfers pausable | No data | Contract | 22 Nov 2026 |
| Address blacklist | No data | Contract | 22 Nov 2026 |
| Upgradeable proxy | No data | Contract | 22 Nov 2026 |
| Source verified | No | Block explorer | 22 Nov 2026 |
| Top-10 holders | 49.2% | Holder distribution | 22 Nov 2026 |
| Liquidity locked | No | LP holders | 22 Nov 2026 |
| Holders | 1034 | Token contract | 22 Nov 2026 |
| Deployed by | 0x61f7d7…2c351a |
| Holders | 1,034 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x206503…81e122 | 11.39% |
| #2 · contract | 0xca5e45…d4cb84 | 9.84% |
| #3 | 0x141b95…ff0d36 | 7.06% |
| #4 | 0xba0a0a…38c3e5 | 4.64% |
| #5 | 0xfd92f4…2a7eda | 3.00% |
This automated check gave Alsa a score of 0 out of 18, and the reason is straightforward: the simulation found that selling is blocked by the contract. In practice, this means that at the time of testing, an automated attempt to sell this token could not be completed, which is the pattern associated with what's commonly called a honeypot. Alongside this, the top 10 wallet addresses hold 49.3% of the total supply, meaning a small number of holders — which may include the contract owner or related wallets — control a large share of tokens and could affect the market significantly if they were able to move them. The contract's source code is also not verified, so the automated check could only read the raw bytecode rather than human-readable code, which limits how much of the contract's logic could be confirmed. Liquidity is not locked, meaning whoever controls the liquidity pool retains the ability to withdraw it, which would affect the ability to trade the token on a decentralised exchange.
It's important to understand what this check does not tell you. This is an automated, mechanical read of the contract's code and on-chain data — it does not assess the team behind Alsa, their track record, the project's tokenomics or business model, legal structure, or anyone's intent. A contract can show no flags and still be tied to a project with no real activity or a team that behaves badly, and conversely, some flags here could in theory reflect an early-stage setup rather than deliberate design. No human has reviewed this token or formed a judgement about it; the result reflects only what the automated scan detected on the date of the check.
Given that selling has been flagged as blocked, it would not be appropriate to treat this as something to test with a small purchase — if the contract genuinely prevents selling, any funds put in would not be retrievable, regardless of the amount. Instead, next steps for due diligence that don't involve putting money at risk include looking up the contract address on the Base block explorer to review any available transaction history and holder activity, searching for the project's official channels and any team disclosures, checking whether the liquidity pool address and its lock status can be independently verified on a site that tracks LP locks, and searching the contract address alongside terms like "honeypot" or "scam" to see whether other users or tools have reported similar findings.
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.