RUG.TOOLS
Stable Token (ST)
0x7d2934b3e48900bf0a3b6f8cbed097cb5b22ffb6Scan results are a snapshot. Select Analyze Again to run a new scan.
Dead / Inactive
The project shows no meaningful activity and is effectively inactive on-chain.
Scanned at 2026-10-22 18:45:46 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Sell check unverified · Token controls unverified · LP protection unverified · Evidence needs refreshing.
Verification gaps (11): Required verification checks are incomplete; category availability does not establish completed verification. · The report evidence is stale or its observation time is invalid; confidence is limited. · On-Chain Contract Checks: Contract runtime was acquired, but its capabilities are not yet verified for this runtime family · More in Evidence & Caveats below.
Evidence-backed reasons, ranked by recorded severity. Open Evidence & Caveats below for complete explanations and limits.
- Critical Red Flag
1. Project Lifecycle
Project appears inactive with no meaningful trading or liquidity.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
- High-Priority Risk
2. Largest Holder Account
One holder account holds 99.9% of supply; independent control is not established.
- Risk Indicator
3. Sampled Holder Accounts
sampled holder accounts hold 100.0% — high concentration.
- Risk Indicator
4. Liquidity
Very thin liquidity ($1,529) — 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.
Bottom line
The project shows no meaningful activity and is effectively inactive on-chain.
Biggest concerns
project lifecycle · holder concentration
Evidence & Caveats 4 recorded reasons · 11 verification gapsClick to expandExpanded
Recorded verdict explanation
The project shows no meaningful activity and is effectively inactive on-chain.
Some checks unverified: Sell check unverified · Token controls unverified · LP protection unverified · Evidence needs refreshing.
1. Project Lifecycle · Critical
Project appears inactive with no meaningful trading or liquidity.
Why it matters: Weakening activity or liquidity can impair exits; deterioration alone is not proof of deliberate fraud.
2. Largest Holder Account · High
One holder account holds 99.9% of supply; independent control is not established.
3. Sampled Holder Accounts · Medium
sampled holder accounts hold 100.0% — high concentration.
4. Liquidity · Medium
Very thin liquidity ($1,529) — 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.
Evidence quality & missing verification
Data available: 3/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.
- The report evidence is stale or its observation time is invalid; confidence is limited.
- On-Chain Contract Checks: Contract runtime was acquired, but its capabilities are not yet verified for this runtime family
- Market data (DexScreener): No active market pair verified
- LP ownership: Liquidity protection is unverified. Position-lock checks are not available for this pool; this verdict does not establish that its liquidity is protected.
- Liquidity depth: Liquidity depth could not be verified
- native honeypot simulation cannot evaluate this market's available route
- critical contract-security fields are unknown
- liquidity protection cannot be evaluated on this chain
- the underlying evidence is stale and has not been re-verified
- Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
Ruggy commentary
“This project is done. Don't step in the trap.”
Follow Rug.Tools & discuss this report
Discuss in Discord ↗Coverage note: Liquidity protection is unverified. Position-lock checks are not available for this pool; this verdict does not establish that its liquidity is protected.
Market snapshot & additional signals
Market snapshot & key evidence
Total tracked liquidity
$1,529.26
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. Earlier or mixed market observations are being retained.
Per-pool amounts were not recorded in this snapshot. The total must not be read as the primary pool's liquidity.
Important signals
Recorded facts · open cards for evidenceSampled holder accounts: 100.0% · lower bound after infrastructure exclusions
No 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.
Single holder holds 99.9% of supply. Currently sits at $1.5K in liquidity, $0 traded in the last 24h, 6 holders. The largest wallet controls 99.9% of supply. The creator wallet could not be verified.
Why this verdict?▾
- Critical overrideProject LifecycleProject appears inactive with no meaningful trading or liquidity.
- + High riskLargest Holder AccountOne holder account holds 99.9% of supply; independent control is not established.
- + ConcernSampled Holder Accountssampled holder accounts hold 100.0% — high concentration.
- + ConcernLiquidityVery thin liquidity ($1,529) — a trading risk (heavy slippage), not proof of a scam.
- No dataContract SecurityRequired contract checks are incomplete; absence of critical flags is not established.
Key Findings
😈 Dead / InactiveSingle holder holds 99.9% of supply.
One holder controlling a quarter of supply can crash the price on exit.
Trading risk: very thin liquidity — even small trades will move the price.
This is a liquidity/slippage risk for traders, not evidence that the token itself is unsafe.
Identified creator wallet currently holds 0% of supply.
This measures only the identified creator wallet; total team or connected-wallet ownership is not established by this metric.
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.
High Concentration. Adjusted concentration excludes identified pools 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
- 0.00%
- 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
1 stored cohort rows
Receipt-level replay was not stored for this snapshot.
Current cohort balances
99.94%
1/1 wallets measured · 0 unknown
Custody coverage
0 custody accounts / markets
0 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x5c9d…2000 · 0.00% current measured holdings
Attribution: routescan-contract-creation. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0x39bf…c17a
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 1 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0xe591…6d6a | 99.94% | #25,551,016 | 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 graph7 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.
0x5c9df6ecea6e3900c7b1ce147173779a83462000
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-10-22 18:45:46 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsNo Coordinated Launch Signal Observed
Module severity describes launch-pattern evidence and does not replace the overall Rug.Tools verdict.
Reconstructed from ERC-20 Transfer logs in the first 5,000 blocks after deployment. Initial distribution includes pools, lockers and other protocol contracts and is not evidence of insider control. Wallet exposure counts only non-contract recipients, and wallets are reported as coordinated only when they acquired supply in the same block.
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.
0x5c9d…462000 · attribution limitedCoverage note: 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
Concentrated-liquidity position ownership and lock protection have not been verified. No protective claim is made without position evidence.
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.