Z On-Chain Risk Check

Gen Z · BSC · 0x9adc3d87e053eee18e3544a0274141bb4969ffff
12 / 18 On-chain Check
Checked 18 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 18 Nov 2026
Buy tax 0% Contract 18 Nov 2026
Sell tax 0% Contract 18 Nov 2026
Admin mint Not present Contract 18 Nov 2026
Transfers pausable Not present Contract 18 Nov 2026
Address blacklist Not present Contract 18 Nov 2026
Upgradeable proxy No Contract 18 Nov 2026
Source verified Yes Block explorer 18 Nov 2026
Top-10 holders 91% Holder distribution 18 Nov 2026
Liquidity locked No LP holders 18 Nov 2026
Holders 1782 Token contract 18 Nov 2026

This contract — Z

Deployed by0xa78f33…d7e8f1
Current ownerNone — ownership renounced
Holders1,782

Largest holders

RankAddressShare
#1 · contract 0x2f3ecd…d0d511 43.09%
#2 · burned 0x000000…00dead 40.00%
#3 0x013cfa…5c1735 1.27%
#4 0x28816c…e29307 1.00%
#5 0xe38537…8c1825 1.00%

What this means

This automated check looked at the contract code and on-chain data for Z (Gen Z) and scored it 12 out of 18. In practical terms, the simulation found the token can currently be sold, with no buy or sell tax detected, and no admin mint function, pause switch, blacklist capability, or upgradeable proxy was found in the contract as of the check date. That means, based purely on what the code allows, the contract owner does not appear to hold obvious levers to block sales, freeze wallets, create new tokens out of thin air, or silently swap in different contract logic later. Verified source code means the contract's human-readable code has been published on the block explorer, so the logic behind these findings can be independently read rather than taken on trust.

Two findings stand out as risk indicators worth sitting with before anything else. First, the top 10 holders control 91% of the supply — a concentration this high means a small number of wallets could sell large amounts at once, which can move the price sharply regardless of anything in the contract itself. Second, liquidity is not locked, meaning whoever supplied the trading pool can withdraw it at any time, which is a separate and common way value can be pulled out of a token even when the contract has no malicious functions at all. Neither of these is a coding flaw; they're structural facts about who holds what, and both sit outside what "no honeypot behaviour detected" is telling you.

It's worth being clear about what this check does not cover. It reads contract mechanics only — it has no view into who the team is, whether they're anonymous, what their track record looks like, how tokens were allocated or vested, whether there's a working product or roadmap behind the token, or what the actual intent of the people running it is. A clean mechanical read and good intentions are two different things, and this check only speaks to the first.

Before putting money in, it would be reasonable to look up the liquidity pool directly on the explorer to see who holds the LP tokens and whether a lock exists anywhere outside what was detected here, to look at the top holder wallets individually and check whether they're exchange addresses, dead wallets, or linked private wallets, and to look for any public information about who operates the project and how. None of this guarantees an outcome either way — it just gives you more of the picture than contract mechanics alone can show.

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