77周年$77
Risk analysis for 77周年 (77) on BNB Chain — contract 0x1949101889795c20a29cf48cf691349ab71d7777. 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 77 is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0x448364734E73014d4A7Bff9B36037f6aba6533c6The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is 77周年?
77周年 ($77) is a BEP-20 token on the BNB Chain blockchain Its primary trading venue is pancakeswap, with roughly $5.75K in live on-chain liquidity. It currently has 255 on-chain holders, and was first traded 4 days old. Rug.Tools' current assessment of 77周年 is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
77周年 (77) is a BNB Chain token analyzed by Rug.Tools. Current status: Multiple health signals are weakening, and the top 10 wallets hold 15.0% of supply, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 17.1% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$5,745 in on-chain liquidity, 255 holders, 3 days old. This page auto-updates as new on-chain data is collected.
Rug.Tools signals
Key statistics
Rug.Tools analysis
Multiple health signals are weakening, and the top 10 wallets hold 15.0% of supply, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 17.1% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot d52c65dc · v3 · scanned 2026-10-02 13:08 UTC · page content updated 2026-10-02 13:08 UTC
Holder distribution
Creator profile
0xe2b5e8ac1225c40b7c6156842f8178467ae14f76Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-09-29 06:09 UTCToken launchedFirst on-chain trading pair opened on pancakeswap.
- 2026-10-02 13:08 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Loading similar BNB Chain tokens…
Learn more
Frequently asked questions
What is 77周年?⌄
77周年 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 77周年 safe?⌄
Current Rug.Tools verdict: Elevated Risk. Multiple health signals are weakening, and the top 10 wallets hold 15.0% of supply, and liquidity is relatively low, so expect slippage when trading, and a launch-pattern cluster acquired 17.1% 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 77周年 have?⌄
Rug.Tools currently sees 255 holders. The top individual wallet holds 3.34% of supply; the top 10 individual wallets together hold 15.00%.
Where is 77周年 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.