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 | 14 Nov 2026 |
| Buy tax | 0% | Contract | 14 Nov 2026 |
| Sell tax | 0% | Contract | 14 Nov 2026 |
| Admin mint | Enabled | Contract | 14 Nov 2026 |
| Transfers pausable | Not present | Contract | 14 Nov 2026 |
| Address blacklist | Not present | Contract | 14 Nov 2026 |
| Upgradeable proxy | No | Contract | 14 Nov 2026 |
| Source verified | Yes | Block explorer | 14 Nov 2026 |
| Top-10 holders | 100% | Holder distribution | 14 Nov 2026 |
| Holders | 1 | Token contract | 14 Nov 2026 |
| Deployed by | 0xb233d1…ce9410 |
| Current owner | 0xff7477…eb47f8 |
| Holders | 1 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xff7477…eb47f8 | 100.00% |
This automated check scanned MKIT's contract code on BSC and found a few things worth understanding plainly. The owner of this contract can mint new tokens at will, which means the total supply is not fixed — new tokens can be created and added to circulation at any time, which can dilute the value of tokens already held by others. The top 10 holders control 100% of supply, and the holder count itself is recorded as 1, meaning virtually all tokens sit in a very small number of wallets (or just one). In practice, this means a very small group — potentially the deployer alone — holds the ability to move or sell a large share of supply, which can affect the market significantly if those tokens are sold. On the positive side, no honeypot behaviour was detected: the simulation showed the token is sellable, and buy and sell taxes are both recorded at 0%. No pausable transfer function or address blacklist capability was found in the contract, meaning that, as of this check, the owner does not appear to hold those two specific controls. The contract source code is verified on the block explorer, meaning the code is publicly readable, which supports transparency but does not by itself indicate anything about how the contract will be used.
It's important to be clear about what this check does not tell you. This is an automated read of contract mechanics only — it looks at what the code technically allows, not who is behind it, what they intend to do, or whether their plans match what's been communicated publicly. It does not assess the project's team, their track record, the tokenomics design, any legal structure, marketing claims, or roadmap. A contract can have no concerning technical flags and still be tied to a project with poor fundamentals, and conversely, a flagged capability does not confirm bad intent — it only confirms the capability exists in the code as written on the date of this check.
Given the concentration figures here, it's worth looking at the chain explorer directly to see exactly which wallets hold the supply, whether any are linked to known exchange or burn addresses, and whether there's been any recent large-scale transfer activity. It's also worth checking whether the minting function has already been exercised, and if so, how often and by how much. Looking for a published audit, an active and responsive community channel, a clear explanation of the mint function's purpose, and any statements from the team about future supply plans would all add useful context that this contract-level check cannot provide on its own.
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.