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 | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | No data | Contract | 22 Nov 2026 |
| Admin mint | Not present | Contract | 22 Nov 2026 |
| Transfers pausable | Enabled | Contract | 22 Nov 2026 |
| Address blacklist | Not present | Contract | 22 Nov 2026 |
| Upgradeable proxy | No | Contract | 22 Nov 2026 |
| Source verified | Yes | Block explorer | 22 Nov 2026 |
| Top-10 holders | 5.6% | Holder distribution | 22 Nov 2026 |
| Liquidity locked | No | LP holders | 22 Nov 2026 |
| Holders | 365 | Token contract | 22 Nov 2026 |
| Deployed by | 0x4eb8e6…874dbb |
| Current owner | 0x4eb8e6…874dbb |
| Holders | 365 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x9abac3…a736a2 | 0.57% |
| #2 | 0x2e5792…eb9df5 | 0.57% |
| #3 | 0xa9ef0b…0e92c6 | 0.56% |
| #4 | 0x9ca19a…3faa9f | 0.56% |
| #5 | 0x7cb41e…78dfb4 | 0.56% |
This automated check scanned the DPMC DEFI contract on BSC and found that transfers can be paused by the owner. In practice, this means whoever controls the contract has a function that can freeze all token movement for every holder, at any time, without needing holder approval. A test transaction simulation showed the token is currently sellable, no minting function was detected (so the owner cannot create new tokens to dilute supply), and no blacklist function was detected (so addresses cannot be individually blocked from trading, at least not through that mechanism). Top-10 wallets hold 5.6% of supply, which is a relatively low concentration compared with many tokens checked. The contract source code is verified on the block explorer, meaning the published code can be read and matches what's deployed, and no upgradeable proxy pattern was detected, so the logic isn't designed to be swapped out later. Liquidity is not locked, however, which means whoever controls the liquidity pool tokens could withdraw the paired funds from the trading pool at a time of their choosing, which would affect the ability to sell at a reasonable price.
It's important to understand what this check does not cover. This is an automated read of contract mechanics only, on the date it was run. It says nothing about who the team behind DPMC is, whether they have a track record, how the tokenomics are structured beyond what's on-chain, whether there's a legal entity behind the project, or what their intentions are. A contract can look clean on paper while still being part of a project with no real plans, and conversely some flagged mechanics exist for mundane operational reasons. No human has reviewed this token or vouched for it; the result is a machine-generated snapshot, not a judgement on trustworthiness.
Before putting money in, it's worth checking who holds the liquidity pool tokens and whether there's any stated plan for locking them, since this is currently unlocked. Look at who owns the contract (is it a multisig, a timelock, or a single wallet?) and whether there's any communication from the team about why pause functionality exists and under what conditions it might be used. Search for the project's social channels, any audits beyond this automated check, and independent community discussion. Check the holder list directly on the block explorer to see how it has changed over time, not just the current snapshot. None of this guarantees an outcome, but it gives a fuller picture than contract mechanics alone can provide.
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.