| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No — transfers blocked | ChainSift simulation | 13 Nov 2026 |
| Buy tax | 0% | Contract | 13 Nov 2026 |
| Sell tax | 0% | Contract | 13 Nov 2026 |
| Admin mint | No data | Contract | 13 Nov 2026 |
| Transfers pausable | No data | Contract | 13 Nov 2026 |
| Address blacklist | No data | Contract | 13 Nov 2026 |
| Upgradeable proxy | No data | Contract | 13 Nov 2026 |
| Source verified | No | Block explorer | 13 Nov 2026 |
| Top-10 holders | 95.9% | Holder distribution | 13 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 13 Nov 2026 |
| Holders | 24 | Token contract | 13 Nov 2026 |
| Deployed by | 0xf3f229…89be16 |
| Holders | 24 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x1f1a04…49252e | 27.88% |
| #2 · contract | 0x322831…d446e6 | 22.45% |
| #3 | 0x80c174…aa273f | 14.32% |
| #4 · contract | 0x01188b…da0613 | 6.77% |
| #5 · contract | 0x121496…1c2519 | 6.48% |
This automated check found that TDSUSDT currently blocks selling: the simulation detected transfers that cannot be completed once a holder tries to exit the position. In practice, this means that any funds used to acquire this token would not be recoverable through a normal sell transaction, regardless of how buy or sell tax percentages are displayed elsewhere. Because this honeypot behaviour was detected, the overall score is capped at zero, and no other finding changes that outcome. Separately, the top 10 wallets were found to hold 95.9% of total supply, meaning a very small number of addresses could affect the token's trading conditions simply by their own actions. The contract source code was not verified on the block explorer, so the check is reading bytecode only — functions such as admin mint, transfer pausing, address blacklisting, or upgradeable proxy logic returned no data, which means their presence or absence could not be confirmed either way, not that they are absent. The liquidity-burned figure of 100% was also recorded, which refers only to the liquidity pool tokens and does not offset the selling restriction identified above.
It's worth being clear about what this check does not cover. This is an automated read of contract mechanics as they exist on-chain at the time of the scan — it does not evaluate who built the token, what their stated plans are, whether any legal entity stands behind the project, or how the stated tokenomics might play out over time. A token can show no flags on a mechanical level and still carry risks tied to team conduct, marketing claims, or future governance decisions, none of which a contract scan can detect.
Given that selling has been blocked by the contract itself, no purchase — test-sized or otherwise — would allow verification of whether the restriction has changed, since any funds placed into the contract would remain there under the same conditions already detected. Instead, next steps that don't involve placing funds at risk include reviewing the contract on a block explorer once/if the source becomes verified, checking whether the project team has published any statement addressing the selling restriction, looking at the distribution and transaction history of the top holder wallets, and searching for independent discussion of this contract address across community channels. Any decision about this token should weigh the fact that a core function — the ability to sell — was not working at the time 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 18 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.