| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | Transfer simulation | 12 Nov 2026 |
| Buy tax | 0% | Contract | 12 Nov 2026 |
| Sell tax | 0% | Contract | 12 Nov 2026 |
| Admin mint | Enabled | Contract | 12 Nov 2026 |
| Transfers pausable | Not found | Implementation code | 12 Nov 2026 |
| Address blacklist | Enabled | Implementation code | 12 Nov 2026 |
| Upgradeable proxy | Yes — a single wallet can replace the code | Proxy contract | 12 Nov 2026 |
| Source verified | Yes | Block explorer | 12 Nov 2026 |
| Liquidity locked | 0.5%, end date unknown | LP holders · TeamFinance | 12 Nov 2026 |
| Holders | 1064 | Token contract | 12 Nov 2026 |
| Deployed by | 0x97e0ce…906417 |
| Code can be replaced by | 0x97e0ce…906417 — a single wallet |
| Current code | 0x2a7dba…05c7bc |
| Holders | 1,064 |
| Rank | Address | Share |
|---|---|---|
| #1 · burned | 0x000000…00dead | 5.282783450356464e+64% |
| #2 | 0x4a22b4…d4ef87 | 1.433664333584785e+63% |
| #3 · contract | 0x97e0ce…906417 | 4.057944997762197e+62% |
| #4 | 0xe0f992…91412f | 7.636634789720496e+61% |
| #5 | 0x4a6615…9eb421 | 6.13716445009277e+61% |
This automated check gave OCEANSv2 a score of 0 out of 12, and the most important finding is that a transfer simulation detected selling is blocked by the contract. In practice, this means wallets that hold the token cannot currently convert it back out, regardless of how buy and sell tax rates are set elsewhere in the code. Alongside this, the contract allows the admin to mint new supply at will, which can dilute existing holdings, and it supports blacklisting specific addresses, which would let the contract owner prevent a chosen wallet from transacting at all. The contract also sits behind an upgradeable proxy, meaning a single wallet holds the ability to swap out the underlying code entirely — including removing or changing any of the mechanics described here — at a later date, without needing holder approval. The liquidity pool shows only 0.5% locked, with no end date found for that lock, so the bulk of the trading liquidity is not shown as secured. Source code is verified on the block explorer, which means the code is readable, but verification alone says nothing about what that code does with the powers above.
It's worth being clear about what this check does not cover. It reads contract mechanics only — the literal functions and permissions written into the code, and how the contract behaved in a simulated transfer. It says nothing about who is behind the project, whether the team's stated plans or roadmap are realistic, how the tokenomics are designed to play out over time, or whether any legal structure or registration exists. No human has reviewed this project, and the automated check cannot assess intent — a contract can have concerning mechanics for reasons ranging from early-stage testing to design choices never meant to be used against holders, and this check cannot distinguish between those cases.
Given that selling is currently blocked, no amount of money put into this token — including a small test purchase — can be assumed to come back out while that condition holds, so that is not a way to verify the finding. Readers who want to look further could check the project's official channels for any statement addressing the blocked transfers, review the liquidity lock terms directly on TeamFinance to see the actual unlock date, look at the holder distribution for concentration in a small number of wallets, and watch the block explorer for any contract upgrade transactions from the proxy admin address. None of this constitutes investment advice, and the findings above reflect only what was detected on the date of this check.
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.