FECLIPSE On-Chain Risk Check

FairEclipse · BSC · 0x4f45f6025be6c65573daa0b9965a75e837848da0
9 / 18 On-chain Check
Checked 21 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 21 Nov 2026
Buy tax 10% Contract 21 Nov 2026
Sell tax 6.6% Contract 21 Nov 2026
Admin mint Not present Contract 21 Nov 2026
Transfers pausable Not present Contract 21 Nov 2026
Address blacklist Not present Contract 21 Nov 2026
Upgradeable proxy No Contract 21 Nov 2026
Source verified Yes Block explorer 21 Nov 2026
Top-10 holders 90.1% Holder distribution 21 Nov 2026
Liquidity locked 68.4% burned LP holders 21 Nov 2026
Holders 20056 Token contract 21 Nov 2026

This contract — FECLIPSE

Deployed by0x1a2e21…41b0a5
Current ownerNone — ownership renounced
Holders20,056

Largest holders

RankAddressShare
#1 · burned 0x000000…00dead 53.87%
#2 · PancakeV1 · contract 0x6f8aed…5a7acd 33.80%
#3 0x8ada39…cf3bd2 0.83%
#4 0x8fa95d…c5dbbf 0.28%
#5 0x5b23ff…c698dc 0.23%

What this means

This automated check scanned FECLIPSE's contract code on BSC and scored it 9 out of 18 on the mechanics it looks for. In practical terms: the simulation found the token can currently be sold, and no admin mint function, transfer pause switch, or address blacklist was detected in the contract, meaning the owner does not appear to have those specific levers to trap holders or create unlimited new tokens. The contract source code is also verified on the block explorer, which allows anyone to read what it actually does rather than trusting a black box. However, the contract does apply a transfer tax of up to 10% (buy tax 10%, sell tax 6.6% at the time of this check), which is taken out of every trade automatically, and this rate could be a fixed feature of the contract or, depending on how it's coded, something an owner function could adjust — this check does not tell you which. Liquidity is 68.4% burned, which reduces (but does not eliminate) the risk of that locked liquidity being pulled, and the top 10 holders together control 90.1% of supply, a concentration level that means a small number of wallets could move a large share of tokens at once, which tends to affect price stability.

What this check does not do is evaluate the people behind FairEclipse, how the remaining tokenomics are structured, whether there's a legal entity behind it, or what the team's actual intentions are. No human reviewed this project — the result comes entirely from automated reading of contract code, tax simulation, and holder data pulled from the chain on the date of the check. A verified source and an absence of flagged functions describes what was not detected in the code itself; it says nothing about off-chain promises, marketing claims, or future behaviour, including whether the tax rate or other parameters could be changed later by whoever holds admin keys.

Before deciding anything, it's worth looking at who holds the top wallets and whether any are labelled as exchanges, team wallets, or locked contracts, since that changes what 90.1% concentration actually means. Check whether ownership of the contract has been renounced or still sits with an active wallet, since that wallet may retain other privileges not captured in this scan. Look at the liquidity lock details directly on the explorer or lock-service page to confirm the burn is real and permanent rather than time-limited. Finally, search for the team, audits, and community discussion independently, since none of that forms part of this contract-only check.

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