Sakura On-Chain Risk Check

サクラ · Base · 0x92878145fa941afccb11e410845216d7e7404080
6 / 10 On-chain Check
Checked 19 Nov 2026. On-chain Check, 10 of the 100-point ChainSift Score — what it covers. Contract function analysis was unavailable for this contract, so that signal is excluded from the total.

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: 2/10 on 13 Nov 2026. Since then: top-10 holders 56% → 15.1%.

Evidence

Risk factorFindingEvidenceDate
Sellable No data Transfer simulation 18 Nov 2026
Buy tax No data Contract 18 Nov 2026
Sell tax No data Contract 18 Nov 2026
Admin mint No data Contract 18 Nov 2026
Transfers pausable No data Contract 18 Nov 2026
Address blacklist No data Contract 18 Nov 2026
Upgradeable proxy No data Contract 18 Nov 2026
Source verified No Block explorer 18 Nov 2026
Top-10 holders 15.1% Holder distribution 18 Nov 2026
Holders 6419 Token contract 18 Nov 2026

This contract — Sakura

Deployed by0x803377…eef159
Holders6,419

Largest holders

RankAddressShare
#1 0x803377…eef159 6.94%
#2 0xa39984…2a8a17 0.95%
#3 0xfa135e…e2908b 0.93%
#4 0x13515b…a04d70 0.90%
#5 0x9a78af…94f934 0.90%

What this means

This automated check scored Sakura 6 out of 10 on Base, but the most important thing to understand is what this score is actually built on: very little. The contract's source code is not verified on the block explorer, which means the automated tooling could not read its functions and could not confirm whether sell transactions succeed, what tax applies to buys or sells, whether the owner can mint new tokens, pause transfers, or blacklist specific addresses. All of these came back as "no data" rather than "clear" — that is a meaningful difference. No data means the check could not look, not that the contract was looked at and found free of these mechanisms. Holder concentration did register: the top 10 wallets hold 15.1% of supply across 6,419 holders, which on its own is not an unusually high concentration, but it sits alongside a contract whose core behaviour remains unverified.

Because this is an automated, mechanics-only check, there's a lot it does not and cannot speak to. It does not assess who is behind the project, whether the team is anonymous or doxxed, how the tokenomics are structured, whether there's a lock on liquidity, what any whitepaper or roadmap promises, or whether marketing claims match reality. A contract can have no detected red flags in its code and still be attached to a project with no real backing, no sustainable plan, or outright misrepresentation elsewhere. None of that is visible from bytecode alone, and no human has reviewed this listing — the result above is generated entirely by automated analysis.

Given that sellability, tax rates, mint permissions, and pause/blacklist functions all came back unverifiable, the sensible next step is to get the contract source verified or find independent confirmation of it before treating any part of this score as reassurance. Since whether the token can even be sold is unknown, this is not a situation where a small test purchase makes sense — if sell behaviour turns out to be restricted, funds placed into the contract in the meantime cannot be recovered. Worth checking separately: whether liquidity is locked and for how long, who holds the largest wallets beyond the top-10 aggregate figure, whether the deployer or owner address has a history with other tokens, and whether the project has been independently verified on Basescan or a similar explorer. Treat the unverified source as the headline fact here, not the numeric score.

Team, tokenomics and legal structure are not assessed here — that is the other 90 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 10 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 Base block explorer. Scores are calculated by fixed rules from that data — no language model decides them. Last updated 19 Nov 2026. A check describes a contract on the date shown; contracts can be changed afterwards.