RUG.TOOLS
PFEAGLE$$PFEAGLE
Risk analysis for PFEAGLE ($PFEAGLE) on Robinhood — contract 0x1a95c10e4839033686225eaad3ac348f0d8edc4f. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-09-22 08:07 UTC
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
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
What is PFEAGLE?
What is PFEAGLE?
PFEAGLE ($$PFEAGLE) is a ERC-20 token on the Robinhood blockchain Its primary trading venue is Uniswap, with roughly $31.60K in live on-chain liquidity. It currently has 76 on-chain holders, and was first traded 1 month old. Rug.Tools' current assessment of PFEAGLE is "Elevated 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
The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable.
Verdict from canonical snapshot dc8ed8e0 · v3 · scanned 2026-09-22 08:07 UTC · page content updated 2026-09-24 12:40 UTC
Holder distribution
Holder distribution
Token activity
Token activity
- 2026-09-21 15:49 UTCToken launchedFirst on-chain trading pair opened on Uniswap.
- 2026-09-24 12:40 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 PFEAGLE?⌄
PFEAGLE 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 PFEAGLE safe?⌄
Current Rug.Tools verdict: Elevated Risk. The published assessment requires holder-concentration recomputation. Displayed figures use the current account-role evidence rules; independent account control remains unverified. Other recorded risks remain applicable. 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 PFEAGLE have?⌄
Rug.Tools currently sees 76 holders. The largest holder account holds 14.45% of supply; the top 10 holder accounts together hold 66.46%. These balances alone do not establish individual ownership or independent control.
Where is PFEAGLE 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.