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 | 2% | Contract | 18 Nov 2026 |
| Sell tax | 2% | 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 | 85.7% | Holder distribution | 18 Nov 2026 |
| Liquidity locked | 100% burned | LP holders | 18 Nov 2026 |
| Holders | 9726 | Token contract | 18 Nov 2026 |
| Deployed by | 0x0e0f1e…6b0271 |
| Current owner | 0x000042…060000 |
| Holders | 9,726 |
| Rank | Address | Share |
|---|---|---|
| #1 · PancakeV2 · contract | 0x266026…cb4a67 | 60.66% |
| #2 · burned | 0x000000…00dead | 11.71% |
| #3 · contract | 0xd14aa1…db2158 | 1.94% |
| #4 · contract | 0x0f8195…9495fb | 1.91% |
| #5 | 0x04b319…0b5b3f | 1.89% |
This automated check scanned the PEIPEI contract on BSC and scored 12 out of 18. In practical terms, the findings show that a test transfer went through successfully, meaning no honeypot behaviour was detected on the date of this check — tokens bought could also be sold. A transfer tax of up to 2% applies on both buying and selling, which is deducted automatically by the contract and goes to a destination defined in the code, not something a holder can opt out of. No admin mint function was found, meaning the owner does not appear able to create new tokens out of thin air and dilute supply. No pause function and no blacklist function were detected, so based on this scan the contract owner does not currently have a coded way to freeze transfers generally or block specific wallets from trading. The contract is also not upgradeable through a proxy, so the underlying code is not set up to be swapped out for different logic later. Liquidity is reported as 100% burned, meaning the LP tokens were sent to a dead address, reducing (though not necessarily eliminating) the risk of the liquidity being pulled by whoever controls it. Holder concentration is high: the top 10 wallets hold 85.7% of supply, which means a small number of addresses could move a large portion of tokens at once, something that can affect price independent of anything in the contract code.
What this check does not tell you is just as important. It reads contract mechanics only — it cannot assess who is behind the project, whether the team has a history of similar launches, how the token's economics are supposed to work long-term, whether any legal entity stands behind it, or what the stated intentions of the deployer are. Source code being verified means the code is readable, not that it has been independently audited or that its logic is free of risks beyond what this automated scan checks for.
Before putting any money in, it is worth looking at who the top 10 holders actually are and whether any are known exchange or team wallets, checking whether the liquidity burn transaction can be independently confirmed on the block explorer, searching for any audit reports from third-party firms, and looking into the team's public presence, if any, and the project's history. Reading the tokenomics documentation, if available, to understand what the transfer tax funds are used for is also worth doing before deciding how to proceed.
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.