| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 9 Sept 2026 |
| Buy tax | 0% | Contract | 9 Sept 2026 |
| Sell tax | 0% | Contract | 9 Sept 2026 |
| Admin mint | Not present | Contract | 9 Sept 2026 |
| Transfers pausable | Not present | Contract | 9 Sept 2026 |
| Address blacklist | Enabled | Contract | 9 Sept 2026 |
| Upgradeable proxy | No | Contract | 9 Sept 2026 |
| Source verified | Yes | Block explorer | 9 Sept 2026 |
| Top-10 holders | 66.9% | Holder distribution | 9 Sept 2026 |
| Liquidity locked | No | LP holders | 9 Sept 2026 |
| Holders | 93706 | Token contract | 9 Sept 2026 |
| Contract deployed | 12 Aug 2026 — 29 days ago |
| Deployment transaction | 0xa30d10…9a9fc6 |
| Deployed by | 0xb66a29…0b2b4e |
| Current owner | 0x725e31…463fd8 |
| Holders | 93,706 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xd4b22f…c0c7bb | 12.30% |
| #2 | 0x9436b7…ec0852 | 8.36% |
| #3 | 0x43d461…2cfd5e | 8.20% |
| #4 | 0x99dc0b…4bbb9a | 7.73% |
| #5 | 0x4674cb…c3f17f | 7.58% |
This automated check of the KITE contract on Ethereum returned a score of 13 out of 18, based on contract mechanics only. A few points are worth translating into plain terms. The contract includes a blacklist function, which means whoever controls the contract retains the ability to block specific wallet addresses from transacting with the token — including, potentially, a wallet you use. No admin mint function was detected, meaning the ability to create new tokens out of thin air was not found on the date of this check. Transfers are not pausable, so the contract owner does not appear to have a switch to freeze all trading network-wide. Buy and sell tax both read 0%, and a transfer simulation found the token sellable, meaning no honeypot behaviour (a setup that lets you buy but blocks you from selling) was detected at the time of testing. Contract source is verified on the block explorer, which allows anyone, including automated tools like this one, to read the actual code rather than a black box. On the more cautious side, liquidity is not locked, meaning whoever supplied the trading pool could withdraw it, and the top 10 holders control 66.9% of supply, which is a high concentration — large holders moving tokens can affect price and liquidity significantly.
It's important to be clear about what this check does not cover. This is a purely mechanical read of the smart contract's code and on-chain data. It says nothing about who is behind the project, whether the team has a track record, how tokens are allocated or vested, what the stated use case or roadmap is, or whether any marketing claims made about KITE are accurate. No human has reviewed this contract or the project behind it — this is an automated scan, and it reflects conditions only as of the date it was run. Contract permissions can also be changed after this check, so findings are a snapshot, not a permanent guarantee.
Before considering any transaction, it would be worth looking into who controls the contract's admin keys and whether they are held by a single wallet or a multisig, checking whether the liquidity pool is locked and for how long via a third-party locker service, reviewing the distribution of the top holders in more detail to see if any are known exchange or team wallets, and searching independently for information about the team, audits, and community discussion of the project.
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.
The other 82 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.