FNTCUSDT On-Chain Risk Check

FNTCUSDT · BSC · 0x42ea9491529699380625045dad04cc46f33a55d4
0 / 18 On-chain Check
Checked 19 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 19 Nov 2026
Buy tax 0% Contract 19 Nov 2026
Sell tax 0% Contract 19 Nov 2026
Admin mint No data Contract 19 Nov 2026
Transfers pausable No data Contract 19 Nov 2026
Address blacklist Enabled Contract bytecode 19 Nov 2026
Upgradeable proxy No data Contract 19 Nov 2026
Source verified No Block explorer 19 Nov 2026
Top-10 holders 99.9% Holder distribution 19 Nov 2026
Liquidity locked No LP holders 19 Nov 2026
Holders 21 Token contract 19 Nov 2026

This contract — FNTCUSDT

Deployed by0x4cd2bd…294413
Holders21

Largest holders

RankAddressShare
#1 0x043349…b3b353 44.58%
#2 0xa60794…e63cda 19.60%
#3 0x4f20ad…899397 13.69%
#4 0x781a60…13aeaf 8.53%
#5 · contract 0x4cd2bd…294413 8.04%

What this means

This automated check scored FNTCUSDT 0 out of 18, and the single most important finding is that selling is blocked by the contract. In plain terms, this means that if tokens are bought, the contract's code prevents them from being sold back — the simulation that ChainSift ran found no working path to exit the position. Because of this, the overall score is capped at zero regardless of any other signal, since the ability to sell is a precondition for everything else to matter. Alongside this, the contract supports blacklisting addresses, meaning the owner has a built-in function to block specific wallets from transacting at all. The top 10 holders control 99.9% of the supply, which means a tiny number of wallets — very possibly including the project team — hold almost everything, so large movements by any one of them could affect the rest of the holders significantly. The contract's source code is not verified, so no one, including this check, can read the actual logic behind the bytecode — this is why several fields above show "no data" rather than a definitive answer. Finally, the liquidity behind the token is not locked, meaning whoever controls it could remove it from the trading pool at any time.

It's worth being clear about what this check does not cover. This is an automated read of the contract's mechanics as they exist on-chain today — it says nothing about who is behind the project, their intentions, their track record, or whether the tokenomics described anywhere (websites, social media, whitepapers) match what the contract actually does. It does not assess legal structure, regulatory status, or whether any marketing claims are accurate. No human has reviewed this token or made a judgement call about it; this is a mechanical scan of code and holder data as of the check date, and conditions can change at any time.

Given that selling is currently blocked, there is no safe way to "test" this token with a small purchase — funds placed into a contract with this behaviour do not come back out through normal selling. If you want to look further, consider having the contract source independently verified and audited by a reputable third party, review the liquidity pool directly on-chain to confirm whether it is locked or owned by a multisig or renounced address, look at the distribution and transaction history of the top holder wallets, and search for any independent, verifiable information about the team or entity behind the project before deciding how 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) and the functions found in the contract bytecode come from ChainSift directly on BSC — our data source returned neither for this contract. 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.