Pepe$PEPE
Risk analysis for Pepe (PEPE) on Ethereum — contract 0x6982508145454ce325ddbe47a25d4ec3d2311933. 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 PEPE is provided by DexScreener.
Market overview
Market data
Trading activity
Markets & liquidity pools
Primary indexed pool
0xA43fe16908251ee70EF74718545e4FE6C5cCEc9fThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Pepe?
Pepe ($PEPE) is a ERC-20 token on the Ethereum blockchain classified as a meme token Its primary trading venue is uniswap, with roughly $34.48M in live on-chain liquidity. It currently has 592,283 on-chain holders, and was first traded 3.5 years old. Rug.Tools' current assessment of Pepe is "Elevated Risk", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
Pepe (PEPE) is a Ethereum token analyzed by Rug.Tools. Current status: The token is actively trading, but the top 10 wallets control 35.5% of supply, and a launch-pattern cluster acquired 18.1% of supply, but independent wallet linkage is not fully corroborated.. Snapshot: ~$34,479,471 in on-chain liquidity, 592,283 holders, 1265 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 the top 10 wallets control 35.5% of supply, and a launch-pattern cluster acquired 18.1% of supply, but independent wallet linkage is not fully corroborated.
Verdict from canonical snapshot 6c9118f7 · v3 · scanned 2026-09-30 23:51 UTC · page content updated 2026-09-30 23:52 UTC
Holder distribution
Creator profile
0xfbfeaf0da0f2fde5c66df570133ae35f3eb58c9aFull creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
- 2023-04-14 17:21 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-09-30 23:52 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 Pepe?⌄
Pepe 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 Pepe safe?⌄
Current Rug.Tools verdict: Elevated Risk. The token is actively trading, but the top 10 wallets control 35.5% of supply, and a launch-pattern cluster acquired 18.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 Pepe have?⌄
Rug.Tools currently sees 592,283 holders. The top individual wallet holds 8.83% of supply; the top 10 individual wallets together hold 35.47%.
Where is Pepe 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.