
币安小蜂
Risk analysis for 币安小蜂 (币安小蜂) on BNB Chain — contract 0x20d375b3fafa56cdb872330450ce0ede88bc7777. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Technical snapshot
Market structure, order flow and published on-chain evidence from one chain-specific snapshot.
Available depth relative to valuation
24h volume divided by liquidity
Transaction split unavailable
Across 1h, 6h and 24h returns
How to read these technicals
Turnover measures trading activity against available liquidity. High turnover can also mean volatility.
Momentum alignment compares overlapping return windows. It is context, not independent confirmation or a safety score.
Holder concentration uses the published report’s classified holder evidence when available.
Freshness is the age of Rug.Tools’ indexed market snapshot, separate from the report scan time.
Price chart
Live price chart for 币安小蜂 is provided by DexScreener.
Market overview
Market data provider unavailable — showing last verified values from 10 hours ago.
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x19d2582728DC065691d2b9A20C87ddF269Fd08c6The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is 币安小蜂?
币安小蜂 ($币安小蜂) is a BEP-20 token on the BNB Chain blockchain Its primary trading venue is pancakeswap, with roughly $75.68K in live on-chain liquidity. It currently has 39,498 on-chain holders, and was first traded 13 days old. Rug.Tools' current assessment of 币安小蜂 is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
币安小蜂 is a BNB Chain token analyzed by Rug.Tools. Current status: The token is actively trading, but one wallet controls 26.0% of supply, and the top 10 wallets hold 29.9% of supply, and a launch-pattern cluster acquired 85.8% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$75,682 in on-chain liquidity, 39,498 holders, 12 days old. This page auto-updates as new on-chain data is collected.
Rug.Tools signals
Key statistics
Rug.Tools analysis

The token is actively trading, but one wallet controls 26.0% of supply, and the top 10 wallets hold 29.9% of supply, and a launch-pattern cluster acquired 85.8% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot 5eddb8d6 · v3 · scanned 2026-10-03 07:22 UTC · page content updated 2026-10-03 07:22 UTC
Holder distribution
Creator profile
0xcd5257fcd1b411e952819549269d4192426adb60Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-09-20 14:15 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-10-03 07:22 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar BNB Chain tokens…
Learn more
Frequently asked questions
What is 币安小蜂?⌄
币安小蜂 is a BNB Chain token analyzed by Rug.Tools using public on-chain data — holders, liquidity, creator wallet activity and contract security signals. This page shows the latest cached analysis and refreshes automatically.
Is 币安小蜂 safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but one wallet controls 26.0% of supply, and the top 10 wallets hold 29.9% of supply, and a launch-pattern cluster acquired 85.8% of supply, but independent wallet linkage is not fully corroborated. No token can be guaranteed safe: verdicts summarize on-chain risk signals only and cannot detect off-chain intent. Always do your own research.
How many holders does 币安小蜂 have?⌄
Rug.Tools currently sees 39,498 holders. The top individual wallet holds 26.01% of supply; the top 10 individual wallets together hold 29.94%.
Where is 币安小蜂 traded?⌄
The primary trading venue detected on BNB Chain is pancakeswap. Use Rug.Tools Swap above to review a routed quote without leaving this report.
How often does this page update?⌄
This page renders from cached data in our database. It refreshes when a new scan runs — either on a scheduled background sync or when a user clicks Refresh above. Opening this page does not trigger a new scan.