RKBFK On-Chain Risk Check

RKBFK · BSC · 0x010af554fe9a8de8463164fcb68cf5be5a39a2ab
0 / 18 On-chain Check
Checked 22 Nov 2026. On-chain Check, 18 of the 100-point ChainSift Score — what it covers. This token can’t be sold, so the check is 0, whatever the other signals show.

Evidence

Risk factorFindingEvidenceDate
Sellable No — transfers blocked ChainSift simulation 22 Nov 2026
Buy tax 0% Contract 22 Nov 2026
Sell tax 0% Contract 22 Nov 2026
Admin mint No data Contract 22 Nov 2026
Transfers pausable No data Contract 22 Nov 2026
Address blacklist No data Contract 22 Nov 2026
Upgradeable proxy No data Contract 22 Nov 2026
Source verified No Block explorer 22 Nov 2026
Top-10 holders 100% Holder distribution 22 Nov 2026
Liquidity locked No LP holders 22 Nov 2026
Holders 5 Token contract 22 Nov 2026

This contract — RKBFK

Deployed by0x9ebac2…b9b000
Holders5

Largest holders

RankAddressShare
#1 0x23c36f…ad8e8f 49.81%
#2 · contract 0xd18240…cbb501 22.33%
#3 · PancakeV2 · contract 0x200514…fac179 17.86%
#4 · contract 0x9ebac2…b9b000 9.38%
#5 0x834149…7d91ed 0.62%

What this means

This automated check scored RKBFK 0 out of 18, and the most important finding is that an automated simulation detected honeypot behaviour: the contract blocks selling. In practice, this means that while a purchase may go through, the code itself can prevent holders from converting the token back out, regardless of how buy or sell tax fields are set elsewhere in the contract. On top of this, the top 10 wallets were found to hold 100% of the supply, across only 5 holders total — this level of concentration means a small number of addresses could move or dump supply in ways that affect every other holder, with no broader distribution to offset it. Liquidity was also found to be unlocked, meaning whoever controls the liquidity pool retains the ability to withdraw it at any time, which can leave a token without a functioning market even if the token contract itself allowed sales. The contract source was not verified on the block explorer, so this assessment is based on bytecode behaviour rather than human-readable code, and several mechanics — admin mint ability, pausable transfers, address blacklisting, upgradeable proxy structure — returned no data, meaning they could not be confirmed either present or absent at the time of this check.

It's worth being clear about what this check does not do. This is an automated read of contract mechanics only — it looks at what the code technically permits, not at who is behind the project, what they intend to do, how the token is distributed or marketed, or whether any legal structure exists around it. No person has reviewed this token, and nothing here speaks to team identity, roadmap credibility, or tokenomics design beyond the raw holder and liquidity data shown.

Given that selling has been blocked by simulation, no purchase — including a small test buy — would be a reliable way to verify this changes, since funds placed into a token that can't be sold remain inaccessible regardless of amount. Readers who want to look further on their own could check the block explorer directly for contract source and transaction history, look at whether liquidity lock services show any lock at all, and search for the contract address and team name across community forums or social channels to see if others have reported being unable to sell. None of this constitutes a recommendation to proceed.

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. The trade simulation (a buy, then a sale an hour later) is run by ChainSift directly on BSC — our data source returned none for this contract. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 22 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.