WHALE On-Chain Risk Check

WHALE · BSC · 0x2b1d6b8475d542d3e1c826d0ff22ea5c2cb57777
12 / 18 On-chain Check
Checked 15 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.

Evidence

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

This contract — WHALE

Deployed by0x93cf6c…f9bd26
Current owner0x000042…060000
Holders24,104

Largest holders

RankAddressShare
#1 0xe024fa…8ac576 50.00%
#2 0x40c7c4…f5c9a0 9.20%
#3 0xebf920…b35d22 8.50%
#4 · contract 0x0000a8…f10000 7.47%
#5 · PancakeV2 · contract 0x61d049…625f91 7.08%

What this means

This automated check of WHALE on BSC scored 12 out of 18, and a few things are worth translating into plain terms. A transfer tax of up to 3% means the contract takes a cut on both buying and selling; this was confirmed directly in the contract code, so it is not something that can change unexpectedly without a contract upgrade (and no upgradeable proxy was detected, meaning the current logic is likely fixed). No admin mint function was detected, which means the owner does not appear to have a built-in way to create new tokens and dilute holders. No transfer pause or address blacklist function was detected either, meaning that, as of this check, there is no visible mechanism letting an owner freeze transfers or block specific wallets from selling. A simulated transfer also completed successfully, which is a basic signal against honeypot behaviour — but this reflects conditions on the day of the check only. Liquidity being 100% burned means the liquidity pool tokens have been sent to a dead address, which is generally read as a sign that liquidity cannot be pulled out by whoever provided it. On the other side, top-10 wallets hold 88.2% of supply, which is a high concentration; large holders moving tokens can affect price and trading conditions in ways smaller holders don't control.

It's important to be clear about what this check does not cover. This is an automated read of the contract's mechanics — the functions it contains, how a test transfer behaves, how liquidity is held, and how supply is distributed across addresses. It says nothing about who is behind the project, whether the team's stated plans or roadmap are realistic, how the token's economics are designed to work over time, whether any legal or regulatory structure applies, or what the people controlling the deployer and top wallets actually intend to do. None of that can be inferred from contract code.

Before deciding anything, it's worth looking at who holds those top-10 wallets and whether any are known exchange, team, or locked-contract addresses rather than individual holders, since that changes what 88.2% concentration actually means in practice. It's also worth checking the project's own communications, any audit reports from named third parties, the history and identity of the deployer wallet, and whether liquidity lock claims can be independently verified on-chain rather than taken from a single source. Re-running a check like this periodically is also sensible, since contract permissions and holder distribution can change over time even when the original deployment looked the same.

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 15 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.