Pepe on Monad$PEPE
Risk analysis for Pepe on Monad (PEPE) on Monad — contract 0xc09c8242eb21b24298303799bb5af402a2957777. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-11-17 20:55 UTC
- 1.Unclassified Contract Concentration
An unclassified contract holds 42.89% of supply. Its purpose and control remain unverified.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
- 2.Largest Holder Account
One holder account holds 42.9% of supply; independent control is not established.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
- 3.Sampled Holder Accounts
sampled holder accounts hold 71.0% — high concentration.
Why it matters: Review the underlying recorded evidence; this does not establish malicious intent.
See 5 additional recorded findings
- 4. Project Lifecycle
Trading activity or liquidity is weakening.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
- 5. Liquidity
Very thin liquidity ($4,729) — a trading risk (heavy slippage), not proof of a scam.
Why it matters: Limited available liquidity can make large trades expensive or difficult to exit; a market quote is not proof of LP protection.
- 6. Coordinated Wallet Activity
Reported historical launch exposure: 23.8% of supply. Evidence confidence: medium. Creator allocations and transfers may be included; purchases, common ownership and insider attribution are not established. A Critical module finding describes potential severity, while the overall verdict requires corroborated evidence. Complete launch coverage and wallet-specific transaction links could change the classification.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
- 7. Historical launch exposure
A sampled launch-window group of 128 tracked wallets reached up to 23.84% of supply.
Why it matters: Historical exposure does not prove common wallet control, and it cannot be added to current holdings.
- 8. Current launch-wallet balances
At least 0.07% of supply measured across 40/128 tracked launch wallets at the recorded observation.
Why it matters: Current balances and historical launch exposure measure different moments. Unmeasured wallet balances are unknown; related wallets are not automatically one owner.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. checks incomplete.
• Required verification checks are incomplete; category availability does not establish completed verification.
• 40/128 launch-wallet balances measured; 88 remain unknown. Present group holdings are not fully measured.
• Unclassified Contract Concentration: An unclassified contract holds 42.89% of supply. Its purpose and control remain unverified.
• Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
LP protection: check the full canonical report for independently verified lock, burn or withdrawal evidence. Indexed wiki flags alone do not prove protection.
Technical snapshot
Trading indicators and observed activity
Technical snapshot
Market data and stored security analysis are separate observations; check their timestamps before comparing numbers.
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 provider unavailable — showing last verified values from 4 hours ago.
Market data
Trading activity
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0x1c5f9a90ff28f9d378b79a4ad400ec0c2beabcc5The page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is Pepe on Monad?
What is Pepe on Monad?
Pepe on Monad ($PEPE) is a ERC-20 token on the Monad blockchain classified as a meme token Its primary trading venue is capricorn-monad, with roughly $4.73K in indexed market liquidity. Its displayed canonical holder snapshot reports 20,910 holder accounts, and was first traded 11 months old. Rug.Tools' stored assessment of Pepe on Monad, scanned 2026-11-17 20:55 UTC, is "High Risk". This verdict reflects the evidence available at the time, not current market conditions.
Rug.Tools signals
Rug.Tools signals
Key statistics
Key statistics
Launch activity
Native receipt, wallet and liquidity custody evidenceNative evidence explorer
Launch, wallet flows & liquidity custody
Inspect what was observed, which balances were measured, and what remains unverified. Timing and transfers alone do not establish common ownership or a sale.
Investigate creator trades & token transfers
Forensic intelligence / Activity
What did the developer actually do?
Separate current holdings, historical launch exposure, verified sales and token transfers. Follow the receipts before drawing conclusions.
- Creator holdings
- 0.00%
- Historical launch exposure
- 23.84%
Saved balance measurement; separate from sale history
Observed launch-group share of total token supply; not every graph node, developer sales or present insider ownership
Developer sales: Insufficient Evidence · Trading integrity: Not Scored. A creator holding 0% does not establish whether tokens were sold or transferred.
Launch evidence
60 stored cohort rows
Interval evidence only; full launch coverage is reported separately.
Receipt-level replay was not stored for this snapshot.
Current cohort balances
At least 0.07%
40/128 wallets measured · 88 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x3b42…148b · 0.00% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xd7dd…cf7d
Launch timeline & receipt references
This older snapshot contains a recipient cohort, not the full receipt timeline. Counts and timing describe only the stored sample. Exact interval supply figures and transaction references remain unknown until a bounded native replay records them.
Pool-by-pool custody & protection
42.89% of token supply in custody · reported role / market
An infrastructure classification does not establish ownership or withdrawal protection for an individual liquidity position.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 40 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0x5ae0…73bc | 0.00% | #37,753,137 | Not stored |
| 0x3bc7…9422 | 0.00% | #37,751,917 | Not stored |
| 0xc219…4f82 | 0.00% | #37,751,924 | Not stored |
| 0xb10a…41b5 | 0.00% | #37,751,802 | Not stored |
| 0xa2b7…19a0 | 0.00% | #37,751,802 | Not stored |
| 0x0106…1051 | <0.01% | #37,751,802 | Not stored |
| 0x7d36…7970 | 0.00% | #37,752,210 | Not stored |
| 0x4bbc…ac89 | 0.00% | #37,751,802 | Not stored |
| 0x5288…3f99 | 0.00% | #37,751,802 | Not stored |
| 0xb6aa…f439 | 0.00% | #37,751,802 | Not stored |
| 0xfcd2…db4d | 0.00% | #37,752,007 | Not stored |
| 0x99b1…828d | 0.07% | #37,752,356 | Not stored |
| 0x0bda…b295 | 0.00% | #37,751,802 | Not stored |
| 0x21db…35eb | 0.00% | #37,751,802 | Not stored |
| 0x8a81…a1a6 | 0.00% | #37,755,706 | Not stored |
| 0x676b…1655 | 0.00% | #37,751,929 | Not stored |
| 0x3598…d2a0 | 0.00% | #37,752,211 | Not stored |
| 0x8a5d…ed2d | <0.01% | #37,752,211 | Not stored |
| 0x09fe…c466 | <0.01% | #37,752,211 | Not stored |
| 0x89af…4e40 | 0.00% | #37,754,418 | Not stored |
| 0x0ce6…0bea | 0.00% | #37,751,810 | Not stored |
| 0xd2ca…7a61 | 0.00% | #37,752,083 | Not stored |
| 0xed4f…b77f | 0.00% | #37,751,993 | Not stored |
| 0x0532…31a9 | 0.00% | #37,751,802 | Not stored |
| 0xc2d2…bd4c | 0.00% | #37,751,930 | Not stored |
| 0xc5f5…2376 | 0.00% | #37,756,325 | Not stored |
| 0xb15e…f1a9 | 0.00% | #37,752,155 | Not stored |
| 0x204a…03bb | 0.00% | #37,754,147 | Not stored |
| 0xfcf6…c10e | 0.00% | #37,752,043 | Not stored |
| 0x5e5c…5bc8 | 0.00% | #37,752,956 | Not stored |
| 0xc432…d475 | 0.00% | #37,751,985 | Not stored |
| 0xecd2…99ea | 0.00% | #37,752,500 | Not stored |
| 0x8877…e8fb | 0.00% | #37,754,024 | Not stored |
| 0x00a4…6186 | 0.00% | #37,752,772 | Not stored |
| 0x26b9…ff19 | 0.00% | #37,752,290 | Not stored |
| 0x0ac5…89e6 | 0.00% | #37,755,436 | Not stored |
| 0x0687…a79d | 0.00% | #37,753,797 | Not stored |
| 0xf351…3fc7 | 0.00% | #37,751,926 | Not stored |
| 0xb5b5…e9b4 | 0.00% | #37,752,806 | Not stored |
| 0xa8f9…4479 | 0.00% | #37,752,481 | Not stored |
Source snapshot: . This evidence explorer does not independently change the Rug.Tools verdict. Existing risk findings, verification gates and source timestamps remain authoritative.
RugGraph / Wallet intelligenceLinked-wallet graph25 wallets · 1 transaction references. Follow the receipts from saved launch evidence.Open wallet graph ↓
01 / Launch activity
Select a wallet to see its activity near token launch. Early receipt of tokens alone does not prove a sniper purchase.
Cyan: tokens received · Amber: tokens moved out · Dashed: deployment. Lines connect wallets to the launch sample; they do not identify who sent the tokens. The first 12 wallets are plotted; every listed wallet can be inspected below.
0x3b427018cd3836bb0d73a859bccf591ef8fe148b
Creator attribution
Balance at last observation
Unknown
Time unavailable · observation, not a live balance
02 / Funding connections
Where did the funding come from?
Follow verified transfers back up to three wallets. Select any connected wallet to explore its evidence.
Enhanced funding history is unavailable on this chain or snapshot. The saved report remains available above.
Evidence first. Ownership stays unproven.
A transfer proves funds moved between addresses. It does not prove they belong to the same person. Known exchange, bridge and pool accounts are marked as infrastructure.
How to read this evidence
Arrows show receipt references associated with the launch sample. They do not identify transfer counterparties or establish common ownership.
An early recipient is not necessarily a buyer or sniper. Outflows may be transfers; these summaries do not establish realized sales.
Balance measurements retain their original timestamps. Historical launch exposure is separate from present holdings.
Funding paths, verified swap activity and volume manipulation require additional transaction evidence. Missing history is unknown.
Source snapshot: 2026-11-17 20:55:27 UTC · Funding research runs only when requested.
Rug.Tools analysis
Rug.Tools analysis

A single holder account holds 42.9% of supply; independent control is not established.
- Unclassified Contract Concentration: An unclassified contract holds 42.89% of supply. Its purpose and control remain unverified.
- Largest Holder Account: One holder account holds 42.9% of supply; independent control is not established.
- Sampled Holder Accounts: sampled holder accounts hold 71.0% — high concentration.
- Project Lifecycle: Trading activity or liquidity is weakening.
- Liquidity: Very thin liquidity ($4,729) — a trading risk (heavy slippage), not proof of a scam.
Verdict from canonical snapshot 1109abd7 · v3 · scanned 2026-11-17 20:55 UTC · page content updated 2026-11-17 20:55 UTC
Holder distribution
Holder distribution
Holder figures from the canonical report; observed 2026-11-17 20:55 UTC. They may be older than the market snapshot.
Only recorded top-ten shares are shown; remaining supply, infrastructure custody, and control are not inferred.
Creator profile
Creator profile
0x3b427018cd3836bb0d73a859bccf591ef8fe148bFull creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2025-11-27 04:14 UTCToken launchedFirst on-chain trading pair opened on capricorn-monad.
- 2026-11-17 20:55 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 Pepe on Monad?⌄
Pepe on Monad is a Monad token analyzed by Rug.Tools using available public on-chain data. Holder observations, indexed market data, and the stored risk verdict may have different observation times.
Is Pepe on Monad safe?⌄
Stored Rug.Tools verdict: High Risk (scanned 2026-11-17 20:55 UTC). A single holder account holds 42.9% of supply; independent control is not established. A stored verdict does not prove current safety or future intent. Always do your own research.
How many holders does Pepe on Monad have?⌄
The displayed canonical report holder data reports 20,910 holders, largest measured holder 42.89% and top ten 70.98%. Holder observation: 2026-11-17 20:55 UTC. These figures are historical measurements, not proof of independent control.
Where is Pepe on Monad traded?⌄
The primary trading venue detected on Monad is capricorn-monad. Review the market and liquidity evidence below; trading venue availability does not establish token safety.
How often does this page update?⌄
This page shows cached reports and indexed market observations. Values change when new evidence is recorded or published; opening the page does not trigger a scan.