RUG.TOOLS
ARCAT (ARCAT)
0x07704b06981ea962b87296362a1281484d160000Scan results are a snapshot. Select Analyze Again to run a new scan.
Scanned at 2026-09-30 01:17:39 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Use Caution
Some checks unverifiedThe 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.
Review the recorded risk breakdown below. Missing or unmeasured evidence is not a clean security check.
Evidence & Caveats 0 recorded reasons · 11 verification gapsClick to expandExpanded
Recorded verdict explanation
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.
Some checks unverified: Token controls unverified · Evidence needs refreshing · Holder evidence incomplete.
Evidence quality & missing verification
Data available: 5/8 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.
- 0/1 launch-wallet balances measured; 1 remain unknown. Present group holdings are not fully measured.
- On-Chain Contract Checks: Required native contract evidence could not be fully verified
- Creator intelligence: Creator attribution unavailable
- Honeypot screening: no router configured for arc. Buying, selling and trading taxes remain unverified.
- critical contract-security fields are unknown
- the underlying evidence is stale and has not been re-verified
- holder concentration requires recomputation from verified infrastructure roles
- 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.
- Contract Security: Required contract checks are incomplete; absence of critical flags is not established.
Ruggy commentary
“Important checks are incomplete or evidence is limited. The recorded verdict does not establish safety.”
Discuss this report
Discuss in Discord ↗5 of 8 analysis modules returned usable evidence on Arc. Some checks remain incomplete. Confirmed risk findings still apply; missing evidence does not establish safety.
Required native contract evidence could not be fully verified
Creator attribution unavailable
no router configured for arc. Buying, selling and trading taxes remain unverified.
Verified below: market observation (Market provider not recorded), ERC-20 metadata, total supply, contract bytecode, proxy slot, owner interface (not exposed — other access controls may still exist).
Recorded market data · separate from security verification
Total tracked liquidity
$50,382.07
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 belowSampled holder accounts: 36.3% · lower bound after infrastructure exclusions
Pool / position identity is not recorded in this summary.
Evidence details
Applies to the measured pool / position only; other liquidity positions require separate evidence. This does not establish overall safety.
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
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.
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. Currently sits at $50.4K in liquidity, $9.9K traded in the last 24h, 6.8K holders. Top holder sits at 19.7%. The creator wallet could not be verified.
Why this verdict?▾
- NeutralLiquidityLiquidity depth looks reasonable ($50,382).
- NeutralProject LifecycleProject is actively trading on-chain.
- No dataContract SecurityRequired contract checks are incomplete; absence of critical flags is not established.
- NeutralLargest Holder AccountLargest sampled holder account holds 19.75%; independent control is unverified.
- NeutralSampled Holder Accounts10 sampled accounts hold 36.31% in total; this is a lower bound when the filtered sample has fewer than ten accounts.
Key Findings
🟡 Use Caution- Liquidity depth looks reasonable.
At least one LP position is locked.
Verify the lock duration on the lock service before relying on it.
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 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
1 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
0/1 wallets measured · 1 unknown
Custody coverage
1 custody accounts / markets
1 without verified protection
Token custody and LP withdrawal protection are separate checks.
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
Pool allocation not established · reported role / market
Market selection alone does not verify LP ownership, locks or the controller of this pool.
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 |
|---|---|---|---|
| 0x9379…2d5c | Unknown | #4,403,799 | 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 graph11 wallets · 0 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.
0x937933e11ad6307ae0d8b8115986e91734be2d5c
Early recipient
Balance at last observation
Unknown
2026-09-30 01:17:36 UTC · observation, not a live balance
No transaction reference was stored for this wallet. No relationship is inferred.
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-09-30 01:17:39 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.
No additional creator signals were reported.
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.
Coverage 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.
99.3% of measured LP is burned.
Ownership, protection & source evidence
99.3% of LP tokens are verified burned. This applies only to the measured pool or position and protects it against holder withdrawal; it does not prevent price losses or every liquidity risk.
Protection applies only to the measured pool or position; it does not establish overall token safety.
Source: On-chain LP holders
Contract & trading controls
ContractContract Controls
Direct contract and security-provider evidence. Unknown capabilities stay unknown and are never silently treated as safe.
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.