RUG.TOOLS
OpenZaps$0xZAPS
Risk analysis for OpenZaps (0xZAPS) on Robinhood — contract 0xdd90bfa4adc7f4401e611abac692d939f9f4cb07. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-09 08:10 UTC
A single holder account holds 48.5% of supply; independent control is not established.
Technical snapshot
Trading indicators and observed activity
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
Price chart
Price chart
Load verified candle history to explore price and volume directly in this report.
Market overview
Market overview
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0xb040f18affd851c6ea02b896b2f846cb77edbb33cc5361f7f8c6d14b87c01573The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is OpenZaps?
What is OpenZaps?
OpenZaps ($0xZAPS) is a ERC-20 token on the Robinhood blockchain Its primary trading venue is uniswap, with roughly $202.50K in live on-chain liquidity. It currently has 1,304 on-chain holders, and was first traded 3 months old. Rug.Tools' current assessment of OpenZaps is "High Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Rug.Tools signals
Rug.Tools signals
Key statistics
Key statistics
Launch activity
Stored funding, acquisition and wallet evidenceRug.Tools analysis
Rug.Tools analysis
A single holder account holds 48.5% of supply; independent control is not established.
Verdict from canonical snapshot dbd67468 · v3 · scanned 2026-10-09 08:10 UTC · page content updated 2026-10-09 08:10 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
0x5a52d4b820ae7f02880d270562950918acb14aa2Full creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-07-21 14:30 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-10-09 08:10 UTCRug.Tools analyzed this tokenFresh on-chain snapshot captured.
Similar tokens
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
Frequently asked questions
What is OpenZaps?⌄
OpenZaps is a Robinhood 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 OpenZaps safe?⌄
Current Rug.Tools verdict: High Risk. A single holder account holds 48.5% of supply; independent control is not established. 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 OpenZaps have?⌄
Rug.Tools currently sees 1,304 holders. The largest holder account holds 48.48% of supply; the top 10 holder accounts together hold 70.83%. These balances alone do not establish individual ownership or independent control.
Where is OpenZaps traded?⌄
The primary trading venue detected on Robinhood is uniswap. Review the market and liquidity evidence below; trading venue availability does not establish token safety.
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.