RUG.TOOLS
ETH Token
0x5fd9f73286b7e8683bab45019c94553b93e015cfScan results are a snapshot. Select Analyze Again to run a new scan.
Scanned at 2026-11-06 08:45:20 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Checks Incomplete
A Healthy rating could not be verified: honeypot status is unknown; contract controls are outside current native analysis coverage; holder concentration is unavailable; no verified locked or burned LP position was detected; required evidence unavailable: metadata. This is not evidence the token is unsafe — the required checks did not resolve.
Evidence-backed reasons in recorded severity order. Historical patterns and verification limits are shown separately.
- Risk Indicator
1. Contract Security
Owner can pause transfers.
Why it matters: Contract privileges or transfer rules can change trading conditions. Review the verified capability and its limitations.
Evidence & Caveats 1 recorded reason · 16 verification gapsClick to expandExpanded
Recorded verdict explanation
A Healthy rating could not be verified: honeypot status is unknown; contract controls are outside current native analysis coverage; holder concentration is unavailable; no verified locked or burned LP position was detected; required evidence unavailable: metadata. This is not evidence the token is unsafe — the required checks did not resolve.
1. Contract Security · Medium
Owner can pause transfers.
Why it matters: Contract privileges or transfer rules can change trading conditions. Review the verified capability and its limitations.
Evidence quality & missing verification
Data available: 1/7 modules. Data availability does not mean every required check was verified.
Confidence describes evidence quality, coverage and freshness.
- Required verification checks are incomplete; category availability does not establish completed verification.
- On-Chain Contract Checks: Required native contract evidence could not be fully verified
- Market data (DexScreener): No active market pair verified
- Holder distribution: Holder coverage requirement was not satisfied
- Token identity: Token identity could not be fully read
- Liquidity depth: Liquidity depth could not be verified
- Honeypot screening: buy simulation did not succeed at tested sizes: 10000000000000000,1000000000000000,100000000000000. Buying, selling and trading taxes remain unverified.
- honeypot status is unknown
- contract controls are outside current native analysis coverage
- holder concentration is unavailable
- no verified locked or burned LP position was detected
- required evidence unavailable: metadata
- Project Lifecycle: Not enough data to judge lifecycle.
- Largest Holder Account: Individual holder data unavailable.
- Sampled Holder Accounts: Top 10 wallet concentration unavailable.
- Liquidity: Liquidity data unavailable.
Ruggy commentary
“Important checks are incomplete or evidence is limited. The recorded verdict does not establish safety.”
Discuss this report
Discuss in Discord ↗Coverage note: Liquidity protection is unverified. No verified locked or burned LP position was established.
Recorded market data · separate from security verification
Primary pool · venue unknown
Not recorded
Total tracked liquidity
Not recorded
Combined across tracked pools. Individual pools can have much less liquidity; the total is not an executable exit quote.
Market snapshot · · Snapshot values are not live quotes.
Per-pool amounts were not recorded in this snapshot. The total must not be read as the primary pool's liquidity.
Important signals
Recorded controls & ownership · evidence scope shown belowNo protective claim without on-chain proof
Risk findings remain visible even when other modules lack evidence. Open the full report for wallet, contract, creator and liquidity sources.
Detailed reportFull analysis & source evidenceWallet links, holder distribution, liquidity protection, creator activity, contract controls and source evidence.Expand full analysis ↓Collapse full analysis ↑
Supplemental intelligence
Provider and wallet context
GMGN intelligence
Independent token signals. The Rug.Tools verdict stays based on its own analysis.
Native launch analysis reconstructs a sampled launch-window wallet cohort as a percentage of token supply. GMGN bundler activity estimates a share of trading volume using its own wallet tags; its observation window and population are not established as equivalent. No native pattern in a sample does not rule out GMGN activity. Neither signal alone proves shared funding, bundle execution or insider ownership.
GMGN has not returned data for this token. Your scan and verdict remain available.
Wallet Trade Context
Loading trade context separately from your scan…
Pending ActivityEXPERIMENTAL
Sampled mempool observations, not continuous monitoring. Transactions may fail, be replaced, be cancelled or never confirm. Simulation does not prove confirmation or a completed trade. Pending evidence never changes the main verdict.
Reading stored pending observations…
Risk Snapshot
Report overviewRisk Snapshot
The most important report signals in one place. Detailed evidence stays below; this presentation does not recompute or alter the canonical Rug.Tools verdict.
Owner can pause all transfers. The creator wallet could not be verified.
Why this verdict?▾
- + ConcernContract SecurityOwner can pause transfers.
- No dataProject LifecycleNot enough data to judge lifecycle.
- No dataLargest Holder AccountIndividual holder data unavailable.
- No dataSampled Holder AccountsTop 10 wallet concentration unavailable.
- No dataLiquidityLiquidity data unavailable.
Key Findings
⚪ Checks Incomplete- Owner can pause all transfers.
Proxy/delegated execution detected.
Execution uses another implementation. Proxy detection alone does not establish whether it can be changed or who controls it; implementation privileges remain subject to separate checks.
No active trading pair found for this token.
No live pool was found on this chain, so the token cannot currently be bought or sold on a tracked DEX. This is normal for pre-launch or abandoned tokens.
Live Market Context
Market & trading
Live Market Context
Price, liquidity, volume, venue and trading-tax context are grouped here instead of being repeated across the report.
Market Snapshot
Market activity
Recent trades and participating wallets · Birdeye
Loaded only when requested. No background refresh.
Holders & connected wallets
Wallet intelligenceWallet & Distribution Intelligence
Current holder concentration, connected-wallet evidence and launch-window coordination are kept together so current ownership is not confused with historical launch exposure.
Not Identified. Adjusted concentration excludes verified protocol reserves and burn sinks; other custody is retained when independent control is unverified.
Connected Wallet Intelligence
Reading cached wallet relationships…
Native 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
- Unknown
- Historical launch exposure
- Unknown
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
0 stored cohort rows
Interval evidence only; full launch coverage is reported separately.
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
Recipient cohort not recorded
Observation time unavailable
Custody coverage
0 custody accounts / markets
0 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x344a…6de9 · Unknown current measured holdings
Attribution: routescan-contract-creation. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0xbe3c…9ce5
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
No position-level custody evidence is stored. This does not establish that liquidity is absent or protected.
Measured wallet balances & transfer evidence
A measured zero balance does not prove a sale. Unknown balances are not zero. Only 0 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|
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 graph1 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.
0x344a908d1a7b7d06b7ad7169c1db81fc9d496de9
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.
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-06 08:45:20 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsNo launch-window Transfer logs were returned; launch exposure could not be verified Missing launch evidence is never interpreted as a clean or low-risk result.
Creator intelligence
Developer intelligenceDeveloper / Creator Intelligence
Creator attribution, current holdings, external creator facts and wallet-link evidence are correlated here without changing the canonical Rug.Tools verdict.
May refer to a different wallet or observation time. Reported exits do not establish verified sales or override measured on-chain holdings.
GMGN supplemental intelligence unavailable for this token right now
Developer network could not be fully verified
Wallet-link evidence is incomplete. Missing evidence is not treated as safe.
Incomplete wallet evidence does not lower the overall risk verdict.
Inspect wallet links & supporting evidence▾
No relationship evidence was strong enough to list.
0x344a…496de9 · attribution limitedCoverage note: No launch-window Transfer logs were returned; launch exposure could not be verified; connected-wallet relationships are still loading.
Wallet relationships are one risk category. The overall Rug.Tools verdict can still be High Risk because of contract controls, trading restrictions, liquidity, holder concentration, or other evidence. A dominant holder is a concentration risk; one large wallet alone is not proof that several wallets are connected.
Presentation-only · does not independently change the Rug.Tools verdict
Liquidity & LP Protection
LiquidityLiquidity & LP Protection
Trading depth and LP ownership/lock evidence are grouped together. Liquidity depth describes trading conditions; LP protection describes whether liquidity ownership can be verified.
LP lock or burn protection has not been verified. Missing evidence does not mean liquidity is unlocked.
Ownership, protection & source evidence
No LP holder or lock data was returned for this token, so liquidity protection is Unknown rather than estimated. Unverified LP is a potential signal only and is not counted as evidence of a rug on its own.
Protection applies only to the measured pool or position; it does not establish overall token safety.
Contract & trading controls
ContractContract Controls
Direct contract and security-provider evidence. Unknown capabilities stay unknown and are never silently treated as safe.
Historical Pattern Review
Historical intelligence
Historical Pattern Review
Optional read-only comparison against archived launches and developer patterns. It never changes the Rug.Tools verdict or risk score.
Challenge this report with historical patterns
Runs only when you ask. It compares stored launch and developer patterns and may add an AI adversarial review. It never changes the Rug.Tools verdict or risk score.
Sources & coverage
Evidence quality
Analysis Coverage
Core report evidence and extended intelligence are separated so a complete core report cannot be confused with an unavailable optional launch-history module.
Usable evidence can be partial. These counts do not mean every contract permission, sell restriction or liquidity position was verified.
Launch history: No launch-window Transfer logs were returned; launch exposure could not be verified. Missing extended evidence is never interpreted as a clean signal.