Clarity,
all the way down.

Start with a target.

Paste a token contract, wallet address or transaction hash and select its blockchain. An address format does not identify the chain or establish whether an account is a token contract.

The published workspace includes a fictional ATLAS case. It is separate from the scanner input. A failed or unsupported request never becomes a made-up result for your address.

Three evidence states.

Observed

Directly represented in the available dataset: a transfer, balance or contract event. Sample observations are explicitly labelled as sample data.

Inferred

A hypothesis drawn from observations, with its reasoning and alternative explanations. Shared funding does not prove common control.

Unavailable

A source is missing, unsupported or failed. An unavailable value is not zero, a clean bill of health, or a completed check.

Open any finding to inspect its source description, snapshot time, prior observation when available, and limitations.

Connections are not identities.

A funding edge records one address sending value to another. A transfer edge records token movement. A candidate cluster combines evidence that may suggest a relationship.

Exchanges, bridges, routers and other shared services can connect strangers. They should not become ownership clusters merely because their customers share a source. Even a non-hub common funder is not conclusive proof of a single controller.

Graph depth describes how many relationships from the selected entity are included. A filtered or bounded graph is not a complete picture of the chain.

The first blocks leave clues.

Launch-window concentration measures transfers or buys in a stated block window. It is distinct from verified private-bundle membership.

A shared block, similar timing or multiple recipients may warrant investigation. Identifying a submitted bundle requires a suitable relay or transaction source; timing alone cannot establish intent. The sample case uses the first three fictional launch blocks.

A lock is one check.

Quoted liquidity, executable depth, position ownership, lock contract and unlock time answer different questions. A dollar value is not a promise that a sale can execute at that value.

Verify the exact lock contract, beneficiary, position and expiry before drawing conclusions. A locked position does not resolve minting permissions, transfer restrictions, taxes, upgrades, other pools or future behavior.

Control lives in code and state.

Contract review needs verified code or reliable decoding, the current implementation behind any proxy, and current permissions. Ownership labels alone cannot establish who can mint, pause, blacklist, change fees or upgrade a contract.

Sell simulation is route-specific and time-specific. It is unavailable in this preview. No safety score is generated from absent checks.

Keep the boundary visible.

A useful scan names its chain, block or snapshot time, indexed range, included sources and failed checks. Partial transfer history can produce incomplete holder counts or balances. Reorganizations, source delays and attribution errors can change a result.

The sample timestamps are fixed scenario times in UTC. They do not indicate a live feed. The optional token endpoint does not supply verified index coverage or lock expiry; the interface retains that limitation beside its response.

Build an investigation.

1. Open the lead finding and inspect its evidence.
2. Trace the relevant entity in Connections; filter relationships or inspect earlier activity.
3. Compare two entities or the original and revised sample snapshots.
4. Select holders to inspect their combined supply share. A selection is not an ownership claim.
5. Save useful evidence, write a journal entry and export a report with the sample status intact.

Use ⌘/Ctrl K or / for quick find. Arrow keys or Tab navigate results. Enter opens an item; Escape closes dialogs. Graph entities support keyboard selection and an equivalent list view.

Your wallet stays yours.

Exploration requires no wallet. Cyclops does not hold private keys or user funds. Wallet verification, when enabled, is a message signature and is distinct from a transaction. A burn-paid pass would require its own explicit transaction review.

Notes, saved items, alert drafts and contribution drafts are stored in this browser. They are not synced or encrypted by the app. Clearing browser storage can remove them; exports give you a separate copy.

Access is separate from rewards.

The planned token tiers are $50 held for Holder and $500 for Pro. A monthly pass paid by burning tokens is Next. Verify launch and contract details on the access page.

Cyclops Eyes rewards reviewed work. Drafting, submitting, approval, any report deposit and confirmed payout are separate states. Holding alone earns no rewards. See Cyclops Eyes and the Live / Next roadmap.