| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | 0% | 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 | 100% | Holder distribution | 22 Nov 2026 |
| Liquidity locked | No | LP holders | 22 Nov 2026 |
| Holders | 11 | Token contract | 22 Nov 2026 |
| Deployed by | 0x322831…d446e6 |
| Holders | 11 |
| Rank | Address | Share |
|---|---|---|
| #1 · contract | 0x322831…d446e6 | 75.91% |
| #2 · contract | 0x0faeb6…2e1aa8 | 9.93% |
| #3 · contract | 0x54cbf8…ba8a4e | 7.45% |
| #4 | 0xcff5db…da2eca | 3.83% |
| #5 · contract | 0xa3996b…789d9c | 2.79% |
This automated check returned a score of 0 out of 18 for JVUSDT, and the most important finding is the simplest one: a simulated sell transaction was blocked by the contract. In practice, this means that if tokens are bought, the contract's own code prevents them from being sold afterwards — this is the pattern known as a honeypot. On top of that, the ten largest holders control 100% of the supply, which on an 11-holder token means the asset is concentrated in a handful of wallets that could move or dump their holdings at will if selling were ever possible. The contract's source code is not verified, so it exists only as bytecode — nobody outside the deployer can easily confirm what the contract actually does beyond what automated simulation can observe. Liquidity is also not locked, meaning whoever supplied the trading pair could withdraw it at any time, leaving no way to exchange the token even if the sell restriction were somehow lifted.
It's worth being clear about what this check does not do. It reads contract mechanics only — things like whether a function exists that blocks transfers, whether tax rates are hardcoded, whether holder balances are concentrated. It does not assess who is behind the project, whether any team claims are accurate, how tokens are meant to be distributed or used, whether there is a legal entity behind it, or what the actual intent of the deployer is. A contract can look mechanically simple and still be tied to a project with no real operations, and conversely some flags here (like unverified source) can appear on contracts for reasons unrelated to malicious intent. This tool cannot tell the difference — it only reports what it detected in the code and in a live buy/sell simulation on the date shown.
Given that selling was blocked in simulation, no amount of money put into this token — including a small test purchase — would be a safe way to verify tradability, because funds sent to a contract that cannot be sold typically stay there. There is no transaction size that makes this check safer to perform manually.
If you want to look further before making any decision, consider checking the block explorer directly for the contract creator's transaction history and any admin functions, searching for whether the project has any independent coverage or audits, checking whether the liquidity pool address and its lock status can be verified on a separate LP-lock tracking tool, and treating the very low holder count and unverified source as points that would need independent explanation before any further action. None of this constitutes investment advice, and nothing here confirms or rules out fraudulent intent — it only reflects what the automated check could detect on this date.
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.