DeepGyre/Scanner/喜羊羊 on BNB Chain

喜羊羊 (喜羊羊)

BNB Chain0xbC4f5C369702A1Dd80EEc6fd497100a60F0b8f78
54/100
risk score — MEDIUM RISK
0.0% / 0.0%
buy / sell tax
$1.89
DEX liquidity
5
times scanned on DeepGyre

Checks

Honeypot (cannot sell)not measured
Cannot sell allno
Owner can mintno
Hidden ownerno
Owner can change balancesno
Blacklist functionno
Transfers can be pausedno
Ownership renouncedyes
Upgradeable proxyyes
Source code verifiedyes
Holders1,672,088
24h volume$615K

What moved the score

FactorImpact
Micro Liquidity ($2)
Below $1K — extreme manipulation risk
+65
Swappable Logic Contract
Implementation can be replaced
+35
Extreme Concentration (100% top-10)
Near total supply in 10 wallets
+35
One wallet holds 95%
A single non-LP wallet holds the majority of the supply
+30
Code clone of failed-sell tokens
Same contract code as 2 other token(s) that could not be sold back in our simulation (2 code siblings in total).
+30
Wash trading (325,380x liquidity)
24h volume far above what the pool can carry
+20
Ownership Renounced
No central control point
-20
No Age Data
Cannot verify contract history
+15

What this scan covers

The scanner reads the token's contract on BNB Chain and runs the checks you see above: can a holder actually sell (the honeypot simulation trades against the same pool a buyer would, without signing anything), what the buy and sell taxes really are when a transfer executes, whether the owner can mint, pause, blacklist or rewrite balances, whether ownership is renounced or behind a proxy, and how deep the liquidity is against how concentrated the largest holders are.

Every check has three possible answers — yes, no, and not measured. A check the contract shape does not allow, or a value the chain did not answer at scan time, prints "not measured" rather than a misleading no. The risk score is a weighted read of these factors, shown with the factors and their impact so the number can be argued with instead of trusted.

Frequently asked

A check says "not measured" — is that bad?

Neither good nor bad: the scan could not read it, so it refuses to guess. Re-scan the token live to try again against the current block.

Does a good score mean the token is safe?

No. It means none of the measured red flags fired. A contract can still be renounced today and its liquidity pulled tomorrow — scores age, checks do not predict.

Why does the page show a stored scan instead of a fresh one?

So opening the page is free of side effects: the scanner's upstream budget is spent when you ask for a live scan, not when someone reads this one.

This is the most recent stored scan, taken 2026-10-22 17:08 UTC (first scanned 2026-10-21 10:38 UTC). A token can change after a scan — re-scan it before acting.

Re-scan 喜羊羊 live →
Descriptive, not advice. Every score is an automated heuristic over public data and can be wrong in both directions. Methodology · Dashboard