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 | Transfer simulation | 18 Nov 2026 |
| Buy tax | 0% | Contract | 18 Nov 2026 |
| Sell tax | 0% | Contract | 18 Nov 2026 |
| Admin mint | Not present | Contract | 18 Nov 2026 |
| Transfers pausable | Not present | Contract | 18 Nov 2026 |
| Address blacklist | Not present | Contract | 18 Nov 2026 |
| Upgradeable proxy | No | Contract | 18 Nov 2026 |
| Source verified | Yes | Block explorer | 18 Nov 2026 |
| Top-10 holders | 98.4% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | No | LP holders | 18 Nov 2026 |
| Holders | 33380 | Token contract | 18 Nov 2026 |
| Deployed by | 0x4def2f…2bc2c4 |
| Current owner | 0x6bf609…3e00b3 |
| Holders | 33,380 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x543714…2bb3a3 | 56.15% |
| #2 · contract | 0x6f3176…7a72b5 | 27.44% |
| #3 · contract | 0x73d8bd…4946db | 13.62% |
| #4 · contract | 0x1ddbbc…b3e694 | 0.33% |
| #5 · contract | 0xcb98c1…08d19e | 0.23% |
This automated check of REKT on BSC scored 12 out of 18, and the details behind that number matter more than the score itself. On the date of the check, the contract did not show mint functions, transfer pausing, or blacklist capability, meaning there's no evidence the owner can create new tokens out of thin air, freeze transfers, or block specific wallets from trading. The simulation also found the token sellable with 0% buy and sell tax, so no honeypot behaviour or hidden tax trap was detected at the time of testing. The contract source is verified, which means the code is publicly readable and not hidden behind an unverified or obfuscated deployment. However, two findings stand out as significant risk indicators: liquidity is not locked, which means whoever controls the liquidity pool could remove it at any time, potentially leaving holders unable to sell at a reasonable price; and the top 10 holders control 98.4% of supply, an extremely high concentration that means a small number of wallets could sell in a way that moves the price sharply, regardless of what the contract code allows or forbids.
It's important to be clear about what this check does not do. Everything above comes from reading the contract's mechanics and simulating a transfer — it does not look at who the team is, whether they've doxxed their identities, what the token's actual purpose or roadmap is, how the supply was distributed before you ever saw it, or whether there's any legal entity standing behind the project. A clean read on mechanics says nothing about intent: a contract with no honeypot code can still be part of a project where insiders simply walk away with the liquidity, since that risk lives in the LP lock status, not the token contract itself. No human has reviewed this token; the findings are generated automatically from on-chain data as it existed at the time of the scan, and they can change if the contract or liquidity position is altered afterward.
Before considering any transaction, it would be worth checking the liquidity pool directly on-chain to see who holds the LP tokens and whether there's any lock or vesting contract involved, looking at the top-10 wallet addresses to see if they're linked to a known team, exchange, or locker contract rather than independent holders, and searching for any public information about who created REKT and what they've said about their own token allocation and liquidity plans.
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.