RUG.TOOLS
GLITCH
Risk analysis for GLITCH (GLITCH) on Arc — contract 0x08adbf431569a1aacac2606d2adcd18f4ebf2a71. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
Scanned 2026-10-12 01:28 UTC
- 1.Holder concentration
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.
Why it matters: This is a recorded report observation, not a prediction of future trading or intent.
- 2.Historical launch exposure
A sampled launch-window group of 49 tracked wallets reached up to 1.95% of supply.
Why it matters: Historical exposure does not prove common wallet control, and it cannot be added to current holdings.
- 3.Reported liquidity depth
$22,364.02 in tracked liquidity in the recorded market snapshot.
Why it matters: Trading depth affects slippage and exit difficulty. Market-reported liquidity does not establish a verified LP lock or current executable quote.
See 2 additional recorded findings
- 4. Top 10 individual wallet concentration
The reported top 10 individual wallets hold 54.47% of supply, using the report's holder classification and coverage.
Why it matters: Concentration can increase potential sell pressure. Wallet addresses do not establish distinct beneficial owners or independent control.
- 5. Creator wallet holdings
The identified creator wallet has 0.83% of supply in the recorded balance observation.
Why it matters: This measures the identified wallet only; it does not prove related-wallet holdings, creator intent, or future sales.
Reliability & unknowns
Low confidence describes evidence coverage, quality and freshness, not token safety. Verification status unavailable.
• The report evidence is stale or its observation time is invalid; confidence is limited.
• 0/49 launch-wallet balances measured; 49 remain unknown. Present group holdings are not fully measured.
LP protection: not verified. Wallet attribution and independent control require separate evidence.
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
Markets & liquidity pools
Markets & liquidity pools
Primary indexed pool
0x278eab5f794ccbaa85dd7cd275e56bf563d8d26e35fd717800f39340f9730c3aThe page opens from Rug.Tools’ indexed snapshot. Load the full pool list only when you need a live provider check.
What is GLITCH?
What is GLITCH?
GLITCH ($GLITCH) is a ERC-20 token on the Arc blockchain Its primary trading venue is uniswap, with roughly $22.36K in live on-chain liquidity. It currently has 868 on-chain holders, and was first traded 1 month old. Rug.Tools' current assessment of GLITCH is "Use Caution", 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
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.83%
- Historical launch exposure
- 1.95%
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
49 stored cohort rows
Receipt-level replay was not stored for this snapshot.
Current cohort balances
Unknown
0/49 wallets measured · 49 unknown
Custody coverage
0 custody accounts / markets
0 without verified protection
Token custody and LP withdrawal protection are separate checks.
Creator provenance
0x211b…0bcc · 0.83% current measured holdings
Attribution: rpc-creation-trace. Identified wallet only; this does not establish total team ownership.
Deployment receipt: 0x4b54…1724
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 40 stored sample rows are listed; aggregate coverage includes missing rows.
| Recipient | Current balance | First position | Receipt references |
|---|---|---|---|
| 0x9b8d…d1c4 | Unknown | #21,758,085 | Not stored |
| 0x2eeb…c774 | Unknown | #21,754,827 | Not stored |
| 0xe45d…8f8c | Unknown | #21,758,637 | Not stored |
| 0x23f4…c5ca | Unknown | #21,754,916 | Not stored |
| 0xf3e0…075e | Unknown | #21,754,989 | Not stored |
| 0x868c…d82f | Unknown | #21,755,370 | Not stored |
| 0x3a57…7192 | Unknown | #21,758,321 | Not stored |
| 0xea47…b87b | Unknown | #21,755,033 | Not stored |
| 0x6a12…a86d | Unknown | #21,755,132 | Not stored |
| 0x0f37…8740 | Unknown | #21,755,076 | Not stored |
| 0xad9b…ef99 | Unknown | #21,755,219 | Not stored |
| 0x1f64…3518 | Unknown | #21,759,025 | Not stored |
| 0x5033…757a | Unknown | #21,754,929 | Not stored |
| 0x805c…c69d | Unknown | #21,755,604 | Not stored |
| 0x0582…0bb5 | Unknown | #21,755,513 | Not stored |
| 0xbfb1…eac7 | Unknown | #21,755,270 | Not stored |
| 0xaf50…7c12 | Unknown | #21,755,774 | Not stored |
| 0xe735…7b02 | Unknown | #21,754,991 | Not stored |
| 0x2da9…0ee4 | Unknown | #21,755,903 | Not stored |
| 0xd926…e644 | Unknown | #21,755,715 | Not stored |
| 0xb536…098d | Unknown | #21,755,657 | Not stored |
| 0x7faa…d4c7 | Unknown | #21,755,657 | Not stored |
| 0x8e51…dac8 | Unknown | #21,755,657 | Not stored |
| 0x7a44…9124 | Unknown | #21,759,040 | Not stored |
| 0xf6c8…a202 | Unknown | #21,755,840 | Not stored |
| 0x23c9…e31b | Unknown | #21,759,458 | Not stored |
| 0x9405…2685 | Unknown | #21,759,017 | Not stored |
| 0x8cff…3da8 | Unknown | #21,755,468 | Not stored |
| 0x4c9a…e6b5 | Unknown | #21,759,521 | Not stored |
| 0xb320…af30 | Unknown | #21,755,680 | Not stored |
| 0xbd84…05fe | Unknown | #21,759,201 | Not stored |
| 0x5b2c…721b | Unknown | #21,755,441 | Not stored |
| 0xd710…4e2c | Unknown | #21,755,320 | Not stored |
| 0x87fb…0965 | Unknown | #21,759,123 | Not stored |
| 0x2c31…3dde | Unknown | #21,756,744 | Not stored |
| 0x2844…c6ce | Unknown | #21,756,466 | Not stored |
| 0x7548…db9f | Unknown | #21,756,108 | Not stored |
| 0xc43a…d516 | Unknown | #21,758,894 | Not stored |
| 0x3862…8bc0 | Unknown | #21,754,757 | Not stored |
| 0xfad6…b1a4 | Unknown | #21,756,915 | 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.
0x211b9e7aa76b38acffa2a27d39f6150190510bcc
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-10-12 01:28:30 UTC · Funding research runs only when requested.
Rug.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 c5c90d29 · v3 · scanned 2026-10-12 01:28 UTC · page content updated 2026-10-12 01:28 UTC
Holder distribution
Holder distribution
Creator profile
Creator profile
0x211b9e7aa76b38acffa2a27d39f6150190510bccFull creator history is currently Solana-only. Multi-chain creator profiles are coming soon.
Token activity
Token activity
- 2026-09-20 00:38 UTCToken launchedFirst on-chain trading pair opened on uniswap.
- 2026-10-12 01:28 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 GLITCH?⌄
GLITCH is a Arc 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 GLITCH safe?⌄
Current Rug.Tools verdict: Use Caution. 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 GLITCH have?⌄
Rug.Tools currently sees 868 holders. The largest holder account holds 34.68% of supply; the top 10 holder accounts together hold 54.47%. These balances alone do not establish individual ownership or independent control.
Where is GLITCH traded?⌄
The primary trading venue detected on Arc 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.