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 | 13 Nov 2026 |
| Buy tax | 0% | Contract | 13 Nov 2026 |
| Sell tax | 0.5% | 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 | 29.1% | Holder distribution | 13 Nov 2026 |
| Liquidity locked | No | LP holders | 13 Nov 2026 |
| Holders | 139616 | Token contract | 13 Nov 2026 |
| Deployed by | 0x58d7c1…397711 |
| Holders | 139,616 |
| Rank | Address | Share |
|---|---|---|
| #1 · burned | 0x000000…00dead | 10.00% |
| #2 · contract | 0x94df62…d74150 | 2.83% |
| #3 | 0xad1e8d…32ae7b | 2.68% |
| #4 | 0x568ee9…c7066a | 2.45% |
| #5 | 0xf6b8b5…2b96ef | 2.29% |
This automated check found that FLOAT could be sold in a simulated transaction on the date of the check, which means no honeypot behaviour was detected at that time. A small transfer tax of up to 0.5% applies on sales, which is a cost but not a blocker. Beyond this, several contract functions — including whether the owner can mint new tokens, pause transfers, or blacklist specific wallets — were not reported by the data source and so could not be scored. This is an important gap: these are exactly the mechanisms that, if present and controlled by an owner, could let that owner later restrict a holder's ability to trade or dilute the supply. Because the contract source code is not verified on the block explorer, this check could only read the raw bytecode, which limits how much could be confirmed either way. Liquidity is also not locked, meaning whoever supplied the trading pool could withdraw it, which would affect the ability to sell on the open market even though the token itself is not currently flagged as a honeypot.
It's worth being clear about what this check does not cover. It only reads contract mechanics as they existed at the time of the scan — it says nothing about who is behind the project, how tokens are allocated or vested, whether there is a working product, or whether any public claims about the team or roadmap are accurate. A contract can look technically unremarkable while still being part of a project with weak fundamentals, undisclosed allocations, or no real activity behind it. None of that is assessed here.
Concretely, before putting money in, it would be reasonable to look at who holds the top wallets (here, the top 10 hold 29.1% of supply — a concentration level worth watching, since coordinated selling by a few large holders can move price sharply), check whether the liquidity pool tokens are held by a known locker contract or sit in an ordinary wallet, and see if the project has published or committed to publishing verified source code, since unverified contracts are harder for anyone to audit independently. It's also worth searching for independent commentary or audits from parties unconnected to the project, checking whether the team is identifiable, and reviewing the token's distribution and vesting schedule if one has been disclosed. None of these steps confirm safety, but they fill in parts of the picture that a contract-mechanics scan cannot reach.
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.