
拉飞奇CZ (拉飞奇)
0x45446329e036a00c75125eeb7da2b52a1dbe7777Scan results are a snapshot. Select Analyze Again to run a new scan.
Scanned at 2026-09-30 23:32:50 UTC
Market conditions can change after a scan. Select Analyze Again to refresh.
Checks Incomplete
A Healthy rating could not be verified: native honeypot simulation cannot evaluate this market's available route; critical contract-security fields are unknown; holder concentration is unavailable; liquidity protection evidence is unavailable; the underlying evidence is stale and has not been re-verified. 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. Coordinated Wallet Activity
A possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
Evidence & Caveats 1 recorded reason · 20 verification gapsClick to expandExpanded
Recorded verdict explanation
A Healthy rating could not be verified: native honeypot simulation cannot evaluate this market's available route; critical contract-security fields are unknown; holder concentration is unavailable; liquidity protection evidence is unavailable; the underlying evidence is stale and has not been re-verified. This is not evidence the token is unsafe — the required checks did not resolve.
1. Coordinated Wallet Activity · Medium
A possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
Why it matters: Historical launch exposure can create concentration risk. It does not establish current balances, common wallet control, or executed bundles.
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.
- The report evidence is stale or its observation time is invalid; confidence is limited.
- Launch-pattern confidence does not verify funding relationships, common ownership or bundle execution.
- 3/255 launch-wallet balances measured; 252 remain unknown. Present group holdings are not fully measured.
- 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
- Creator intelligence: Creator attribution unavailable
- Liquidity depth: Liquidity depth could not be verified
- Honeypot screening: router could not quote a buy (no V2 pair / no liquidity). Buying, selling and trading taxes remain unverified.
- native honeypot simulation cannot evaluate this market's available route
- critical contract-security fields are unknown
- holder concentration is unavailable
- liquidity protection evidence is unavailable
- the underlying evidence is stale and has not been re-verified
- Largest Holder Account: Individual holder data unavailable.
- Sampled Holder Accounts: Top 10 wallet concentration unavailable.
- Liquidity: Liquidity data unavailable.
- Project Lifecycle: Not enough data to judge lifecycle.
- 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 ↗1 of 7 analysis modules returned usable evidence on BNB Chain. Some checks remain incomplete. Confirmed risk findings still apply; missing evidence does not establish safety.
Required native contract evidence could not be fully verified
No active market pair verified
Holder coverage requirement was not satisfied
Creator attribution unavailable
Liquidity depth could not be verified
router could not quote a buy (no V2 pair / no liquidity). Buying, selling and trading taxes remain unverified.
Coverage note: Liquidity protection is unverified. The market snapshot did not identify a primary trading pool for this token; LP lock or burn protection cannot be evaluated from this report.
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 belowHistorical transfer exposure; purchases, current holdings and common ownership are separate findings.
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.
A Healthy rating could not be verified: native honeypot simulation cannot evaluate this market's available route; critical contract-security fields are unknown; holder concentration is unavailable; liquidity protection evidence is unavailable; the underlying evidence is stale and has not been re-verified. This is not evidence the token is unsafe — the required checks did not resolve. A launch-wallet pattern was recorded; that pattern alone does not verify funding relationships, common ownership or bundle execution. The creator wallet could not be verified.
Why this verdict?▾
- + ConcernCoordinated Wallet ActivityA possible coordinated early-buyer pattern was observed; wallet coordination and insider attribution are not confirmed.
- No dataLargest Holder AccountIndividual holder data unavailable.
- No dataSampled Holder AccountsTop 10 wallet concentration unavailable.
- No dataLiquidityLiquidity data unavailable.
- No dataProject LifecycleNot enough data to judge lifecycle.
- No dataContract SecurityRequired contract checks are incomplete; absence of critical flags is not established.
Key Findings
⚪ Checks IncompleteNo 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.
These candidate observations do not establish current top-holder rankings. Use the separately measured creator balance for current creator holdings.
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
- 26.89%
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
60 stored cohort rows
Interval evidence only; full launch coverage is reported separately.
Receipt-level replay was not stored for this snapshot.
Current cohort balances
At least 2.33%
3/255 wallets measured · 252 unknown
Custody coverage
0 custody accounts / markets
0 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
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 |
|---|---|---|---|
| 0x606c…d004 | Unknown | #124,996,551 | Not stored |
| 0x853d…740d | Unknown | #124,996,482 | Not stored |
| 0xafba…bf64 | Unknown | #124,996,667 | Not stored |
| 0x61a7…79fe | Unknown | #124,996,667 | Not stored |
| 0xa9c9…aa3d | Unknown | #124,996,018 | Not stored |
| 0xe6d6…a8a1 | Unknown | #124,996,632 | Not stored |
| 0xfce4…c4b5 | Unknown | #124,996,632 | Not stored |
| 0x49d5…4820 | Unknown | #124,996,627 | Not stored |
| 0x45b9…7a6b | Unknown | #124,996,627 | Not stored |
| 0x58ef…e6c6 | Unknown | #124,996,482 | Not stored |
| 0x0193…42f3 | Unknown | #124,996,019 | Not stored |
| 0x2bd2…4b04 | Unknown | #124,996,945 | Not stored |
| 0x873a…1a00 | Unknown | #124,996,250 | Not stored |
| 0x865f…be23 | Unknown | #124,996,661 | Not stored |
| 0x9185…cea5 | Unknown | #124,996,590 | Not stored |
| 0x5ef2…ef29 | Unknown | #124,995,993 | Not stored |
| 0x6b8f…78b7 | Unknown | #124,996,018 | Not stored |
| 0x4be0…4e76 | Unknown | #124,995,951 | Not stored |
| 0xa456…6be8 | Unknown | #124,996,120 | Not stored |
| 0x61c0…b5f6 | Unknown | #124,995,951 | Not stored |
| 0x437a…6c77 | Unknown | #124,996,660 | Not stored |
| 0x1caf…eb5e | Unknown | #124,996,525 | Not stored |
| 0x9c8d…85a4 | Unknown | #124,996,907 | Not stored |
| 0xa416…d90e | Unknown | #124,996,639 | Not stored |
| 0x79c7…8163 | Unknown | #124,995,915 | Not stored |
| 0xd87a…0c51 | Unknown | #124,995,913 | Not stored |
| 0x6075…fc4c | 0.94% | #124,995,886 | Not stored |
| 0x1161…4360 | Unknown | #124,997,105 | Not stored |
| 0xef39…9c2e | Unknown | #124,996,116 | Not stored |
| 0x8e82…b844 | 0.85% | #124,995,886 | Not stored |
| 0xc4a2…994b | Unknown | #124,996,418 | Not stored |
| 0x1c17…b738 | Unknown | #124,996,764 | Not stored |
| 0x4ca8…0a92 | Unknown | #124,996,914 | Not stored |
| 0x8713…09f5 | Unknown | #124,996,617 | Not stored |
| 0x8aaf…94a6 | Unknown | #124,996,042 | Not stored |
| 0xdb2f…7899 | Unknown | #124,996,748 | Not stored |
| 0xa4a7…dd5c | Unknown | #124,996,801 | Not stored |
| 0x88bf…18fa | Unknown | #124,996,761 | Not stored |
| 0x8024…08c3 | Unknown | #124,996,789 | Not stored |
| 0xb072…82da | Unknown | #124,996,881 | 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 graph28 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. The first 12 wallets are plotted; every listed wallet can be inspected below.
0x606cb3cac9291693f18972a96273eec67a0cd004
Early recipient
Balance at last observation
Unknown
2026-09-30 23:32:34 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 23:32:50 UTC · Funding research runs only when requested.
Launch activity
Launch exposure, linked wallets and current holdingsHigh Launch-Concentration Signal
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 grouped by same-block transfer timing. Transfers may be allocations or distributions; they do not by themselves establish purchases, common ownership, shared funding or bundle execution.

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
Wallet activity patterns detected
Wallet-pattern evidence was recorded. Shared ownership and creator control are not established by this summary.
Launch-window patterns and wallet-link evidence use separate samples. No launch pattern in one sample does not rule out wallet links in another. Timing or a funding link alone does not prove common ownership or executed bundle purchases.
Inspect wallet links & supporting evidence▾
- • 65 wallets received transfers in 25 same-block clusters
Coverage note: connected-wallet relationships are still loading.
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.
