KISHU On-Chain Risk Check

KISHU 纪州犬 · BSC · 0x0516996aafd5fc12ecbbe7064934328f629f7777
12 / 18 On-chain Check
Checked 20 Nov 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers.

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.

Previous check: 13/18 on 17 Nov 2026. Since then: top-10 holders 55.9% → 87%.

Evidence

Risk factorFindingEvidenceDate
Sellable Yes Transfer simulation 20 Nov 2026
Buy tax 2% Contract 20 Nov 2026
Sell tax 2% Contract 20 Nov 2026
Admin mint Not present Contract 20 Nov 2026
Transfers pausable Not present Contract 20 Nov 2026
Address blacklist Not present Contract 20 Nov 2026
Upgradeable proxy No Contract 20 Nov 2026
Source verified Yes Block explorer 20 Nov 2026
Top-10 holders 87% Holder distribution 20 Nov 2026
Liquidity locked 100% burned LP holders 20 Nov 2026
Holders 9270 Token contract 20 Nov 2026

This contract — KISHU

Deployed by0x8e26bd…d128b7
Current owner0x000042…060000
Holders9,270

Largest holders

RankAddressShare
#1 · PancakeV2 · contract 0x6eb47d…f7481c 61.83%
#2 · burned 0x000000…00dead 11.66%
#3 0x914615…27179a 2.65%
#4 0x92d7dc…97f797 2.29%
#5 0xaeef91…31a2a8 1.87%

What this means

This automated check of KISHU on BSC found no honeypot behaviour: the simulation shows the token can be bought and sold, and a 2% tax applies in each direction, which is taken by the contract and not something the owner can arbitrarily raise on this chain's current configuration. No mint function was detected, meaning no mechanism was found that would let the contract owner create new tokens out of thin air and dilute holders. Transfers were not found to be pausable, and no blacklist function was detected, so nothing in the contract as read appears to let an admin freeze transfers generally or block specific wallets from moving or selling their tokens. The contract is not upgradeable through a proxy, so the logic deployed is what will keep running rather than being swappable later by whoever controls it. Liquidity is shown as 100% burned, meaning the LP tokens that would let someone pull the trading pool out from under holders are not present in a holdable wallet. Holder concentration, however, is high: the top 10 addresses control 86.5% of supply, which means a small number of wallets can move price substantially if they choose to sell, independent of anything in the contract code.

It's worth being clear about what this does not cover. This is an automated read of contract mechanics as deployed on-chain on the date of the check — it does not assess who the team behind KISHU is, whether they have a track record, what the stated use case or tokenomics roadmap actually involves, or whether any marketing claims match reality. Verified source code means the code is readable, not that its intent has been judged. A contract can show none of the red-flag mechanics above and still carry risk from concentrated ownership, coordinated selling, or simply from being a speculative asset with no underlying demand.

Before acting on this, it's worth checking the liquidity lock or burn directly on BscScan to confirm the LP address and confirm it genuinely holds no claimable balance, rather than relying on a summary. Looking at the top holder wallets individually — their transaction history, whether they're exchange or contract addresses, and whether they've been accumulating or moving tokens recently — can give more context on the concentration figure. Searching for the project name alongside independent community discussion, rather than official channels alone, and checking whether the contract or team has any prior history under a different name are also reasonable next steps. None of this constitutes a recommendation to buy, hold, or sell.

Team, tokenomics and legal structure are not assessed here — that is the other 82 points of the ChainSift Score. How this check works and what it misses.

Watch this contract

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 send one confirmation message and nothing else until something changes.

We checked 18 points out of 100.

A deep check also reviews the project's public materials, team, tokenomics and disclosures.

Related guides

Contract data read from GoPlus Security and the BSC block explorer. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 20 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.