Oyster Coin$🦪
Risk analysis for Oyster Coin (🦪) on Ethereum — contract 0x24c2c6f74f7d34664d85b98bdde5b6048420476c. 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
Trading activity
Markets & liquidity pools
Primary indexed pool
0x46f6d5ee8e41571dda007150829c20ed84aa8129ec4da38fe63d23465be56682The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Oyster Coin?
Oyster Coin ($🦪) is a ERC-20 token on the Ethereum blockchain Its primary trading venue is uniswap, with roughly $20.12K in live on-chain liquidity. It currently has 367 on-chain holders, and was first traded 7 days old. Rug.Tools' current assessment of Oyster Coin is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Oyster Coin (🦪) is a Ethereum token analyzed by Rug.Tools. Current status: Multiple health signals are weakening, and liquidity is relatively low, so expect slippage when trading, and possible coordinated launch activity was detected.. Snapshot: ~$20,121 in on-chain liquidity, 367 holders, 3 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 a launch-pattern cluster acquired 53.5% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot afb7394c · v3 · scanned 2026-09-28 03:03 UTC · page content updated 2026-09-30 22:40 UTC
Holder distribution
Creator profile
0x292187a85ebb4fed06262b9a86c5728eda23df61Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2026-09-27 19:05 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-09-30 22:40 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
Compared using stored market cap, launch age and trading venue. Similarity is not a safety rating.
Finding comparable tokens…
Learn more
Frequently asked questions
What is Oyster Coin?⌄
Oyster Coin is a Ethereum 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 Oyster Coin safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but a launch-pattern cluster acquired 53.5% 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 Oyster Coin have?⌄
Rug.Tools currently sees 367 holders. The top individual wallet holds 2.93% of supply; the top 10 individual wallets together hold 13.01%.
Where is Oyster Coin traded?⌄
The primary trading venue detected on Ethereum is uniswap. 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.