# Book a demo
Source: https://docs.rover.inc/contact/book-a-demo



Book a demo: [cal.com/sophialatessa/onboarding-to-rover](https://cal.com/sophialatessa/onboarding-to-rover)


# Talk to us
Source: https://docs.rover.inc/contact/email



Email: [hi@rover.inc](mailto:hi@rover.inc)


# Bookmarks
Source: https://docs.rover.inc/core/bookmarks



Bookmarks let you pin important on‑chain entities so they are always one click away in the sidebar.

## What are bookmarks?

A bookmark is a shortcut to anything you investigate often—addresses, assets, transactions, views, or folders of related items. Bookmarks live in the **Bookmarks** section of the sidebar and give you a curated list of high‑value entities, separate from ad‑hoc searches.

Each entry shows a colored dot and label, such as "PENGU," "USDT," or "jaredfromsubway.eth," so you can quickly recognize what you saved.

<img alt="Bookmark Main" />

## Creating and organizing bookmarks

You can bookmark items from detail pages, tables, or other parts of Rover using the bookmark icon or context actions. Once bookmarked, the item appears in the sidebar list, where you can:

* Drag and drop to reorder bookmarks within a folder.
* Create folders (for example, "Sophia's Folder") to group related entities like wallets you monitor or assets you trade.
* Mix different entity types in a single folder so your investigation workspace mirrors how your team actually works.

Folders display a count of items they contain, helping you keep large bookmark sets manageable.

<img alt="Creating Bookmark" />

## Using bookmarks in daily workflows

Bookmarks are designed for speed during investigations and monitoring.

* Click any bookmark to open its detail page or associated view in the main panel.
* Use bookmarks as a starting point when building searches—open a bookmarked address, copy its label or address, and drop it into the CMD‑K terminal.
* Combine bookmarks with views and labels so your most important wallets, contracts, and assets are always at your fingertips.

Over time, bookmarks become a personalized control center for your on‑chain work, giving you a fast way to return to the entities they care about most.

<img alt="Sidebar Bookmarks" />


# Command Menu
Source: https://docs.rover.inc/core/cmd-k



The search terminal is Rover's command palette for the blockchain: open it with **CMD‑K** to define rich, structured searches across transactions, addresses, assets, and blocks.

## Overview

Everything in Rover starts from the search terminal. It lets you turn natural questions into precise queries, so you can slice the chain by wallet behavior, asset flows, fee usage, and more from a single interface. Searches you build here power views and detail pages throughout the product.

<img alt="Cmd K Open" />

<Note>
  The search terminal supports both precise, building‑block searches and an optional Semantic search mode for natural‑language queries. If you prefer to start from plain language, see [Semantic Search](https://docs.rover.inc/core/semantic-search) for details.
</Note>

## Using the search terminal

You can work with the search terminal entirely from the keyboard or with your mouse, depending on your preference.

<Tabs>
  <Tab title="Keyboard">
    * Press **CMD‑K** to open the search terminal from anywhere in Rover.
    * Use **↑** and **↓** to move through suggested categories, building blocks, and values.
    * Press **TAB** or **ENTER** to select the highlighted suggestion and add it to your query.
    * Type logical operators like `AND`, `OR`, and `NOT`, or use parentheses `(` `)` to group building blocks.
    * Hit **CMD‑ENTER** to run the current search and open the results view.
  </Tab>

  <Tab title="Mouse">
    * Click the search bar or search icon in the header to open the terminal.
    * Click a search category (Transactions, Addresses, Assets, or Blocks) to start a guided search.
    * Click building blocks in the list to add them to your query, then select values from the suggestions that appear.
    * Use the inline chips to remove or adjust individual building blocks with a click.
    * Click **Search** or the confirmation button in the terminal footer to execute your query.
  </Tab>
</Tabs>

## Search categories

Rover organizes on‑chain data into four search categories: **Transactions**, **Addresses**, **Assets**, and **Blocks**. When you open the terminal, you can either start typing or pick a category first to see the building blocks available for that type of object.

Each category exposes its own set of searchable properties, such as `Transaction Fee`or `Block Number`, represented visually as building blocks in the terminal. Categories are color‑coded so you can quickly see which "family" a search belongs to as you compose it.

## Building blocks

A **building block** is a property you can filter on within a category, like `Transaction Fee`, `From`, `Asset`, or `Block Number`. Think of them as Lego bricks: each block represents one constraint, and combining blocks defines the slice of the chain you care about.

You can scroll or use the arrow keys to browse all building blocks for the current category directly inside the terminal. Multiple blocks from the same category can be combined to create expressive searches without writing code.

## Combining blocks with operators

The terminal supports logical operators such as `AND`, `OR`, `NOT`, and parentheses `(` `)` for grouping. This makes it possible to express queries like "transactions with high fees AND from a specific address, but NOT interacting with a given contract."

Blocks must come from a single category in any given search, *transaction blocks with transaction blocks, asset blocks with asset blocks*, and so on, so your query always targets one type of object at a time. The color of each token in the query line helps you see at a glance that your building blocks all belong to the same family.

## Syntax sugar and smart paste

The terminal automatically cleans up and completes what you type so your query stays valid, even if you do not explicitly enter every operator.

<Tip>
  You can paste a transaction hash, address, or token identifier directly into the terminal, and Rover will detect what it is and route you to the appropriate search or detail page.
</Tip>

## Ways to use the terminal

There are three main ways to build searches:

* **Type to search**: Start typing and let the terminal suggest matching building blocks, categories, and values inline.
* **Browse by category**: Select a category first for a guided experience; inside each building block, suggested values help you refine your search.
* **Natural language translator**: Use plain language to describe what you are looking for, and Rover converts it into a structured set of building blocks.

Once your query looks right, press **CMD‑ENTER** to run it and load the results where you can sort, save, and continue your exploration.

<Note>
  Once you are comfortable with manual building blocks, you can also turn on Semantic Search <kbd>CMD</kbd> <kbd>I</kbd> to describe what you want in plain language and let Rover build the query for you. Learn more in the [Semantic Search ](https://docs.rover.inc/core/semantic-search)page.
</Note>

### Example: building an asset‑scoped transaction search

This example walks through building a transaction search filtered to a specific set of assets using the CMD‑K terminal.

<img alt="Cmd K Example" />

<Steps>
  <Step title="Open the terminal">
    Press **CMD‑K** or click the search bar in the header to bring up the search terminal.
  </Step>

  <Step title="Pick a category">
    Use your keyboard and press **<kbd>↓</kbd>** or your mouse, and select Transactions as your search category so you are querying transaction objects.
  </Step>

  <Step title="Add an asset building block">
    With Transactions selected, choose the **Asset** building block to constrain results to transactions involving particular tokens.
  </Step>

  <Step title="Select one or more assets">
    * Start typing a token symbol or address (for example, USDT or PYUSD) and select it from the favorites or suggestions list.
    * Repeat to add additional assets so the query reads like "Transactions · Asset = USDT, PYUSD, WBTC, …".
  </Step>

  <Step title="Review the resulting blocks">
    Notice how each selected asset appears as a chip in the query line and the terminal now shows transaction‑specific building blocks you can add next, such as `Amount` or `Base Fee per Gas`.
  </Step>

  <Step title="Run the search">
    * Press **CMD‑ENTER** or click **Search** to execute the query and load a view of all transactions that match your asset filters.
  </Step>
</Steps>

This pattern applies to any category: start in the right family (Transactions, Addresses, Assets, or Blocks), add the building blocks that matter, layer on values, and then run the search when it looks right.


# Address Detail Page
Source: https://docs.rover.inc/core/detail-pages/address/contract



## Account Detail Page purpose

Use the Address Detail Page when you need to understand “who is this account, what does it hold, and what has it been doing recently?”. The layout matches other Rover detail pages so you can move smoothly between addresses, assets, transactions, and blocks in the same panel.

## Header and core metadata

At the top, the page shows an **Address** badge, the primary label (for example, “jaredfromsubway.eth”), and quick actions such as copy link or bookmark. The metadata panel includes:

* Address and Address Type: the address in truncated form (0xae2…e13) and its type (Account, Contract), with copy and deep‑link controls.
* Label: ENS or your private/public label
* Net Worth and Balance: estimated portfolio value in USD and a summary of core balances, such as total ETH and the count of other assets.

Additional fields show Holds (highlighting notable assets or positions), Total Fees Used (in native and USD values), and Views, which indicates how many workspace views reference this address. “Add Properties” lets you add additional metadata to the detail page.

<img alt="Account Props" />

## Transactions section

The Transactions section lists recent activity where this address appears as a participant.

Key columns include:

* Transaction Hash: truncated hash linking directly to the Transaction Detail Page.
* Date: relative time since each transaction was confirmed (for example, “5 minutes ago”).
* From (and additional columns in the full view, such as To or Description) that show how the address interacted in each transaction.​

The **Expand** control opens this table into a full view and enables you to sort, filter, or configure the table as you'd like.

<img alt="Account Txns" />

## Assets section

The Assets section shows what the address currently holds, giving a quick portfolio snapshot. The table includes:

* Address: asset avatar and name that link to the corresponding Asset Detail Pages.
* Asset Symbol: the short symbol used throughout Rover tables and filters.
* Asset Type: classification such as Token or NFT.

A TOTAL row at the bottom summarizes how many distinct assets the address holds.

<img alt="Account Assets" />

## Customization and workflows

Like other detail pages, the Address view supports account customization through properties, labels, and bookmarks. From here you can move into related entities, clicking a transaction hash opens Transaction Detail, clicking an asset opens its Asset Detail Page, letting investigations flow naturally between addresses, assets, and blocks.

## Smart Contract Detail Page purpose

The Address Smart Contract Detail Page gives a complete view of a contract address, including ownership, activity, assets it holds, verified source code, bytecode, and callable functions and events.​

This page answers “what is this contract, who deployed it, what does it hold, and how does it behave on chain?” for any address identified as a contract. It mirrors layout and navigation patterns from other Rover detail pages so users can move between contracts, transactions, and assets without changing workflows.

### Header and core metadata

The header shows the address label (for example, “FiatTokenProxy”) and a badge indicating that the entity type is an Address. Core metadata includes:

* Address
* Address Type
* Label
* Deployer
* Net Worth
* Balance
* Views

“Add Properties” lets you add additional metadata to the detail page, similar to custom fields in other productivity tools.​

<img alt="Smart Contract Props" />

### Transactions

The Transactions section surfaces recent on‑chain activity involving the contract, scoped to transactions where the address appears as a participant. The table includes:

* Transaction Hash
* Date
* From / To

The “Expand” control opens the full table view.

<img alt="Smart Contract Txns" />

### Assets

The Assets section lists tokens and other assets currently held by the contract. Columns include:

* Address
* Asset Symbol
* Asset Type

A TOTAL summary row reflects the number of distinct assets in the table, giving a quick snapshot of what the contract controls.

<img alt="Smart Contract Assets" />

### Source Code

When source verification is available, the Source Code section displays one or more files (for example, “SHIB.sol”) in a tabbed code viewer. The left rail lists files; selecting a file renders its Solidity source with syntax highlighting and scrolling in the main pane.​

This view is read‑only and optimized for inspection, mirroring familiar code viewers in developer tools so auditors and engineers can quickly scan contract logic, modifiers, and events without leaving Rover.

<img alt="Smart Contract Source Code" />

### Bytecode

The Bytecode section shows the deployed bytecode for the contract as a monospaced, scrollable block.

<img alt="Smart Contract Bytecode" />

### Functions & Events

The Functions & Events section exposes the contract’s ABI, organized into callable functions and emitted events. Key elements include:

* Search: you can search for the name of certain functions or events
* Read Functions: a grouped list of view/pure functions (for example, TradingOpen, \_maxTxAmount, balanceOf, decimals, owner, pair) each showing if the function is `view`, `nonpayable`, or `payable`
* Events and write functions: when available, additional groups list non‑constant functions and events with matching controls.

<img alt="Smart Contract Events" />

<Info>
  We will be further developing this section, and at the moment, you will only be able to view the function's signature.
</Info>

### Navigation and workspace behavior

From the Address Smart Contract Detail Page, users can navigate to related entities, for example:

* Clicking the Deployer opens that address’s detail page.
* Clicking a transaction hash opens the Transaction Detail Page.
* Clicking an asset row opens the corresponding Asset Token or NFT Detail Page. ​


# Asset Detail Page
Source: https://docs.rover.inc/core/detail-pages/asset-detail-page



## Asset types

There are two types of assets in Rover:

* **Token**: ERC-20 or other fungible tokens
* **NFT**: Non-fungible tokens (ERC-721, ERC-1155, etc.)

The Asset NFT Detail Page provides a complete view of a specific NFT, including its media, collection metadata, trait breakdown, and on‑chain activity. ​

## Token Detail Page purpose

The Asset Token Detail Page is designed to answer “what is this token, who holds it, and what is it doing right now?” for any supported asset contract. It gives analysts and operators a single place to inspect token‑level properties while retaining drill‑down links into addresses and transactions.​

<img alt="Asset Token Props" />

### Header and primary metadata

The header surfaces the asset name (for example, “USD Coin (USDC)”), the asset type (Token vs. other asset classes). Core metadata includes:

* Asset Address
* Asset Symbol and Type: symbol (USDC) and high‑level asset type (Token, NFT collection, etc.) used across Rover tables and filters.
* Price and Total Supply: latest tracked price in USD and the current total supply of the token

“Add Properties” lets you add additional metadata to the detail page.

### Addresses section

The Addresses section lists wallets and contracts that currently hold the token, giving quick answers to “who owns this asset?” It is organized into an address table with columns for Address, Label, and Balance, plus an aggregate TOTAL row at the bottom representing the sum of balances in the current view.​

Each row shows the address with a hover copy action, its workspace label (for example, “+ Custom” for user‑defined labels), and the current token balance formatted with thousands separators. The “Expand” control opens the table in the full-screen view.

<img alt="Asset Token Addresses" />

### Address labels and customization

Labels in the Addresses table work like tags. They can be created inline, edited, and reused across the workspace. Creating or editing a label here updates the label everywhere that address appears, allowing teams to maintain a single source of truth for counterparties such as exchanges, internal wallets, and contracts.

<img alt="Asset Token Label" />

### Transactions section

The Transactions section shows the most recent on‑chain activity involving this asset, scoped to transfers and contract interactions.

The table includes the following columns:

* Transaction Hash
* Date
* Description: a short, human‑readable summary such as “0x… called function …” that is generated from decoded calldata and log events, similar to how other Rover detail pages summarize on‑chain calls.

From the Asset Token Detail Page, users can navigate to different detail pages by clicking on the hyperlinks. Clicking an address cell opens the Address Detail Page for that wallet or contract, while clicking a transaction hash opens the Transaction Detail Page, mirroring navigation patterns described in Rover’s transaction detail documentation.​

<img alt="Asset Transactions" />

## NFT Detail Page purpose

This page answers “what is this NFT, what collection is it from, and what has happened to it on chain?” for any supported token ID. It follows the same interaction patterns as other Rover detail pages.

<img alt="Nft Props" />

## Header and core metadata

The header shows the NFT media on the left and a short collection description on the right so users can quickly recognize the asset and understand its context. Primary metadata includes:

* NFT Collection: the parent collection name (for example, “LilPudgys”) with verification status when applicable.​
* Floor Price and Total Supply: the current collection floor price in the native chain currency and the total number of tokens in the collection.
* Address: the collection contract address, displayed in shortened form with a quick‑copy action and link to the collection or contract detail view.

## Properties and custom fields

Below the main metadata, “Add Properties” lets workspaces attach additional structured data to the NFT, similar to custom fields for issues or projects in Linear. These properties are workspace‑scoped and can be reused in filters, views, and automations wherever the NFT appears in Rover.

## Attributes section

The Attributes section surfaces the NFT’s trait data, for example, `BACKGROUND` → Mint, `HEAD` → Beanie Gray, enabling fast visual scanning and comparison across tokens in the same collection.

<img alt="Nft Attributes" />

## Activity section

The Activity section lists the most recent on‑chain events involving this specific NFT, such as sales, transfers, or mints. The table includes:

* Type: high‑level event type (for example, Sale, Transfer, Mint) derived from decoded logs.
* Description: a human‑readable summary, such as “0x540…2f5 purchased from 0x0db…5af,” including links to buyer and seller address detail pages.
* Date

  <img alt="Nft Activity" />

## Navigation and interactions

From the Asset NFT Detail Page, users can jump to related entities to continue investigations: clicking the NFT's address opens the Contract Detail Page, and clicking an activity row’s address link opens the Addre Detail Page.


# Block Detail Page
Source: https://docs.rover.inc/core/detail-pages/block

The Block Detail Page gives a focused view of a single block, including its metadata, miner rewards, gas usage, and all transactions it contains.

## Page purpose

Use the Block Detail Page when you need to answer “what happened in this block, who produced it, and which transactions were included?”. It follows the same layout as other Rover detail pages so you can quickly pivot between blocks, transactions, addresses, and assets without changing context.​

<img alt="Block Props" />

## Header and core metadata

At the top, the page shows the Block label (for example, “Block #24,213,271”) and a badge indicating that this entity is a Block. The properties show metadata such as:

* Block Hash
* Date
* Transaction Count: the total number of transactions included in the block.

Additional fields summarize who produced the block and how much gas was used: Miner, Total Miner Reward (in ETH and USD), Total Gas Used, and Views, which shows how many workspace views reference this block.

You can click the `+ Add Properties` button to see add or remove information from the detail page.

## Transactions section

The Transactions section lists every transaction included in the block.

<img alt="Block Txns" />

## Navigation and workflows

From a Block Detail Page, you can move directly into related entities by clicking transaction hashes or participant addresses to open their Transaction or Address Detail Pages in the same panel system. This makes it easy to start from an anomalous block (for example, unusual gas usage) and quickly drill into individual transactions, counterparties, and assets involved.​


# Transaction Detail Page
Source: https://docs.rover.inc/core/detail-pages/transaction



## Overview

Rover's transaction detail pages cover a rich amount of metadata to understand exactly what happened in a transaction.

## Properties

The properties area at the top of the transaction detail page will show you important metadata about the transaction. You can click the `+ Add Properties` button to see add or remove information from the detail page.

<img alt="Transaction detail page properties panel showing key metadata fields" />

## Transaction Summary

The Transaction Summary is generated by Rover's own trained models on blockchain data, providing a human-readable explanation of what happened in the transaction, aggregating calls, events, and balance changes into a single narrative. It highlights the primary caller, the key contracts involved, and the overall outcome so you can understand complex flows without stepping through every low-level detail.

Use this section to quickly answer questions like "What was this transaction trying to do?" and "Which contracts and tokens did it touch?"

<img alt="Transaction Summary section showing an AI-generated narrative of the transaction" />

## Asset Flow

The Asset Flow section summarizes the high-level movement of value within a transaction, showing who sent assets, who received them, and which fees were paid. It presents each leg of the flow as a natural-language sentence so you can understand the transaction at a glance, without parsing raw logs.

Each row displays the sending account, the receiving account (if applicable), and the asset amount transferred or fee paid. Use this section to quickly answer questions like "Who paid whom?" and "What did this wallet spend on this transaction?"

<img alt="Asset Flow section summarizing who sent and received assets and fees in the transaction" />

## Asset Updates

The Asset Updates section breaks down how balances changed for each participant in the transaction. For every address involved, Rover lists the net change per asset, making it easy to verify debits, credits, and gas usage.

Negative amounts indicate assets leaving an address (for example, a token transfer or gas payment), while positive amounts indicate assets received. This view is especially useful when debugging complex transactions or confirming that a transaction's observed balance changes match expectations.

<img alt="Asset Updates section showing per-address net balance changes by asset" />

## Subtransactions

The Subtransactions section breaks the transaction into its individual internal calls, showing how value and control moved between contracts over time. Each row represents a call between addresses, including who initiated it, which contract was called, and what assets (if any) were transferred.

Expanding a subtransaction reveals additional detail, making it easier to trace multi-step interactions, debug routing flows, or understand how a router or aggregator executed a particular operation.

Additioanlly, if you click into the hyperlink transaction hash, we have built dedicated subtransaction detail pages, which allow you to dive into the subtransaction in greater detail.

<img alt="Subtransactions table listing internal calls within the transaction" />

## Events (Developer)

The Events section exposes the raw on-chain logs emitted during the transaction, decoded using the contract’s ABI where available. For each event, Rover shows the contract, event name, topics, and decoded parameters so you can inspect the exact data emitted on-chain.

This view is designed for developers who need to validate protocol behavior, confirm integration expectations, or debug unexpected outcomes at the log level.

<img alt="Events section showing decoded on-chain logs for the transaction" />


# Labels
Source: https://docs.rover.inc/core/labels-bookmarks



Labels let you attach human‑readable context to on‑chain entities so addresses are easier to recognize, filter, and share across Rover.

## What are labels?

A label is a short piece of metadata you attach to an address, such as "cbBTC," "My Wallet," or an ENS name. Labels turn anonymous addresses into recognizable entities and make it easier to understand who is involved in a transaction or view.

Rover organizes labels into **Private**, **Public**, and **Requests** tabs so you can control who sees which annotations in your workspace.

<img alt="Labels Main" />

## Private, public, and requested labels

* **Private**: Only you can see and use these labels. They are ideal for personal notes or experiments.
* **Public**: Shared across your workspace so everyone benefits from the same naming and tagging of important addresses.
* **Requests**: Proposed labels that are waiting for review or approval. The Rover team will review labels and approve accordingly to ensure accuracy.

Within each tab, you see rows of addresses with their associated labels and any verification badges or ENS names.

<Note>
  We encourage people to submit labels as it improves the Rover experience for everyone. If a label is submitted, we will review it within 24 hours.
</Note>

## Creating and editing labels

You can create or edit labels from many places in Rover:

* From an address detail page, add or update the label next to the address name.
* From the Labels panel, click into a row to edit the text or add an additional custom label chip.

Changes are applied everywhere that address appears: in tables, views, detail pages, and search suggestions, keeping your naming consistent across the product.

<img alt="Editing Labels" />

## Using labels in searches and views

Labels integrate tightly with the CMD‑K search terminal and tables.

* Start typing a label name in the search terminal to quickly filter for transactions, addresses, or assets that carry that label.
* Use label‑aware building blocks (for example, participants or holders) to target groups of labeled addresses in your searches.
* In address tables, add label‑related columns so you can scan large tables and immediately see which rows belong to key counterparties.

<img alt="Labels In Searches" />

## Collaboration with labels

Labels act as a lightweight directory for your on‑chain counterparties. Teams can:

* Standardize names for exchanges, custodians, internal wallets, and partners.
* Use public labels to align searching and reporting around the same set of entities.
* Track pending or proposed labels in the Requests tab before making them visible to everyone.

Over time, this shared label system becomes a living map of the addresses your organization cares about, embedded directly into Rover's search, views, and detail pages.


# Semantic Search
Source: https://docs.rover.inc/core/semantic-search



Semantic search is an optional mode in the CMD‑K terminal that turns natural‑language questions into structured Rover queries, so you do not have to start by thinking in building blocks and operators.

<img alt="Iss" />

## What semantic search does

When the semantic search toggle is on, the terminal interprets your free‑form text and builds the corresponding legos for you. It understands entities like ENS names, token symbols, function selectors, addresses, blocks, and views, then snaps them into the right filters with appropriate operators and value types.

Instead of manually assembling `Transaction Fee | is at or above | 0.01 ETH`, you can type "transactions with fees above 0.01 ETH," and semantic search generates the filters needed to match that intent.

## Working with on‑chain entities

Semantic search recognizes common on‑chain identifiers and metadata to speed up query construction.

* ENS names with autocomplete and resolution, so typing "vitalik" suggests `vitalik.eth` and resolves the address.
* Popular tokens from the canonical token registry (stablecoins, wrapped tokens, DeFi, meme, and exchange tokens), so "USDC transactions" becomes an `Asset | is | USDC` filter with the correct logo and address.
* Function selectors and names, so phrases like "transactions calling function 0xa9059cbb," "function equals transfer," or "function contains swap" become function filters in the Transactions category.

Because these entities are interpreted before filters are created, the resulting legos use canonical addresses, symbols, and metadata.

## Smarter filters, ranges, and logic

Semantic search can infer comparison operators, numeric ranges, and boolean logic directly from your wording.

* Range phrases such as "blocks with base fee between 50 and 150 gwei" are turned into two filters: one "at or above" 50 and one "at or below" 150.
* Queries like "blocks with miner reward above 2 ETH," "blocks with gas used over 30,000,000," or "blocks with over 200 transactions" map to greater‑than filters on the correct block fields.
* Statements such as "USDC transactions but NOT from 0x123…" or "(failed or value above 10 ETH) and gas below 30 gwei" are turned into grouped logic using AND, OR, and NOT.

Semantic search also distinguishes between similarly named properties on different categories (for example, block gas vs transaction gas, block base fee vs transaction base fee) so filters land where you expect.

<img alt="Iss Example" />

## Using @ for views and ENS

The **@** symbol provides a fast way to reference views and ENS names in your query.

* Type `@` to search for and insert a **view** as input to a building block, such as `Participants @Engineering Wallets`, instead of listing individual addresses.
* Type `@` followed by an ENS name, like `@vitalik.eth`, to resolve and reference that address directly in your filters.

This keeps complex searches readable while letting you reuse existing address sets and identities.

<img alt="At Symbol" />

## Example queries

Semantic search supports both simple and complex patterns.

**Transaction filters**

* "Transactions from 0xd8da6bf26964af9d7eed9e03e53415d37aa96045."
* "Show transactions to 0xd8da6bf26964af9d7eed9e03e53415d37aa96045."
* "Get transactions sent by 0x742d35Cc6634C0532925a3b844Bc9e59…."
* "Get transactions received by 0x742d35Cc6634C0532925a3b844Bc9e59…."

Each becomes a Transactions query with `From`, `To`, or `Participants` filters set to the specified address.

**Address + balance with views**

* "Find addresses from Metamask view with balance over \$10,000."
* "Show Metamask addresses with balance above \$5,000."
* "Get addresses from Metamask Swap view with balance exceeding \$1,000."
* "Addresses in Metamask view with more than \$50,000."

These are interpreted as Address queries that apply the named view and combine it with a USD balance range filter.

You can mix these patterns with token, block, and function phrases. For example, "USDC transactions above \$10,000" or "blocks with base fee above 100 gwei" and semantic search will create the corresponding structured filters.

## Performance and instant patterns

For very simple inputs, semantic search returns results immediately by recognizing hashes, addresses, or "show all" patterns without extra steps. As legos are generated, they will appear one by one in the query bar, making it easier to understand how your plain‑language request maps to Rover's structured search model.


# Sharing
Source: https://docs.rover.inc/core/sharing



Sharing in Rover makes it easy to bring teammates into the same context—whether you are working from a view, a table, or a detail page.

## What you can share

Users can share three main types of links:

* **Views** – any saved search on the Views page.
* **Tables** – any results table, including unsaved searches, via the page URL.
* **Detail pages** – any transaction, address, asset, NFT, or block detail page using the share control in the header.

Each link preserves the current context so collaborators land on the same data you are looking at.

## Sharing views

From the Views page, use the row action menu or toolbar share option to open the share dialog for a specific view. Copy the link and send it to teammates; when they open it, they see the latest data for that saved search with the same filters and layout.

Because views are saved searches, shared links always reflect real‑time chain data rather than a static snapshot.

<img alt="Sharing Modal" />

## Sharing tables via URL

Any table in Rover, whether it comes from a saved view or an ad‑hoc CMD‑K search, can be shared simply by copying the URL from the browser. The URL encodes the current query, filters, and pagination so recipients see the same table configuration when they open it.

This is useful for quickly sharing one‑off investigations without creating a full view.

## Sharing detail pages

Every detail page (such as an asset panel for `USD Coin`) includes a share icon in the top‑right corner of the header. Clicking this icon copies a link that opens the same detail view, including properties, labels, and recent activity, so others can jump straight into the entity you are analyzing.

Sharing detail pages is ideal when you want teammates to focus on a specific wallet, contract, asset, or transaction without navigating through search first.

<img alt="Sharing Copy" />


# Tables
Source: https://docs.rover.inc/core/tables



## Table type

There are four different table types in Rover. Depending on your query, you will get back a specific type of table results:

<div>
  <div>
    <div>
      <span>Table</span>
    </div>

    <div>
      <span>Description</span>
    </div>
  </div>

  <div>
    <div>
      <span>Transactions Table</span>
    </div>

    <div>
      <span>A list of transactions.</span>
    </div>
  </div>

  <div>
    <div>
      <span>Addresses Table</span>
    </div>

    <div>
      <span>A list of addresses, including accounts and smart contracts.</span>
    </div>
  </div>

  <div>
    <div>
      <span>Assets Table</span>
    </div>

    <div>
      <span>A list of assets, including tokens and NFTs.</span>
    </div>
  </div>

  <div>
    <div>
      <span>Blocks Table</span>
    </div>

    <div>
      <span>A list of blocks.</span>
    </div>
  </div>
</div>

For each table, the properties change according the the metadata associated with that specific search category.

<img alt="Table Types" />

## Default properties

Each table has different default properties that will appear as columns. All of the tables have the same design—the only difference is the type of data you are looking at.

<img alt="Dropdown Columns" />

## Manipulating tables

For any table, you can shrink or grow columns, move columns around, or use the action bar to manipulate the table.

### Sort

Using the action bar, you can use the dropdown menu to sort properties within the table.

<Note>
  Some columns in these tables can't be sorted. If you need a sortable property that isn't available yet, [let us know](mailto:hi@rover.inc).
</Note>

### Add or remove properties

Using the action bar, you can use the dropdown menu to add or remove properties within the table.

### Adjust columns

Drag a column header to rearrange its position in the table. Hover over a header edge to resize the column, or double‑click that edge to automatically fit its contents.


# Views
Source: https://docs.rover.inc/core/views



Views are saved searches that stay in sync with the chain and give teams a reusable home for their investigations. They capture your query, table layout, and filters, then refresh live as new blocks are mined so the data is always up to date.

## What is a view?

Views allow you to save searches built in the command menu and reuse them across Rover. The best part is that views dynamically update with the blockchain, so you can set them up once and watch them refresh in real time as new blocks are mined.

Views live on the Views page, where they are grouped by search category type (Transaction Views, Address Views, Asset Views, Block Views). Each view is essentially a named, shareable slice of the chain that your entire team can rely on.

## Creating a view

To create a view, start from a search:

1. Open the command menu (CMD‑K) and create a search using building blocks.
2. In the action bar above the results table, click **Save as View**.
3. Give the view a descriptive name, such as "USDT Transactions" or "Engineering Wallets."
4. Click **Save** to create the view.

The new view appears on the Views page and will continue to update as the underlying on‑chain data changes.

<img alt="Views Save As View" />

## Finding and managing views

To find all the views you have created, navigate to the **Views** page from the sidebar. There, you will see every view organized by category tab, making it easy to jump between transaction, address, asset, and block views.

When you hover over a view, quick actions let you rename, duplicate, share, or delete it without leaving the list. Opening a view lets you change filters, building blocks, or columns; Rover will show when there are unsaved changes, and you can update the view configuration so everyone sees the new definition.

## Views as building blocks

Views can be used as inputs inside other searches, which is where they become especially powerful. For example, suppose you created an Address View called **Engineering Wallets** and want to find all transactions involving any address in that view.

* Start a new **Transactions** search.
* Add the **Participants** building block.
* In the Participants input, search for and select the **Engineering Wallets** view instead of pasting individual addresses.

Press <kbd>CMD</kbd>‑<kbd>ENTER</kbd> and you get a table of all transactions that involve any address in the Engineering Wallets view, without having to maintain a long list of addresses by hand.

<img alt="Views Bb" />

### View types and input compatibility

Views can only be used in building blocks whose input type matches the view's underlying entity. In the example above, using Engineering Wallets worked because Participants expects addresses as its input and Engineering Wallets is an address view.

If a building block expects assets or blocks, only views of that same type can be passed in as inputs. This keeps searches well‑typed and ensures results remain predictable as views evolve.

## Views in tables

Any time you run a search and view results in a table, you can add **View** as a column. If a row is part of one or more views you have created, those view names will appear in that column so you can see exactly which saved searches that row belongs to.

This makes it easy to answer questions like "which of my monitoring views is this transaction part of?" directly from the table, without leaving your current workflow.

<img alt="Views Table Cloumn" />


# Concepts
Source: https://docs.rover.inc/getting-started/concepts



<br />

<br />

<Container>
  <section>
    <div>
      <div>
        <h3>Cmd-K</h3>

        <p>
          Open cmd-K to search. Combine building blocks to ask complex questions—fast.
        </p>

        <p>
          <a href="https://docs.rover.inc/core/cmd-k">Learn more</a>
        </p>
      </div>

      <div>
        <img alt="Command menu (Cmd-K) showing the search terminal interface" />
      </div>
    </div>
  </section>
</Container>

<Container>
  <section>
    <div>
      <div>
        <h3>Tables</h3>

        <p>
          Filter and sort results. Add context with columns for transactions, assets, addresses, and blocks.
        </p>

        <p>
          <a href="https://docs.rover.inc/core/tables">Learn more</a>
        </p>
      </div>

      <div>
        <img alt="Tables interface showing filtered and sorted results" />
      </div>
    </div>
  </section>
</Container>

<Container>
  <section>
    <div>
      <div>
        <h3>Detail Pages</h3>

        <p>
          Click into any item to see full details. Jump between related objects to follow the chain of activity.
        </p>

        <p>
          <a href="https://docs.rover.inc/core/detail-pages">Learn more</a>
        </p>
      </div>

      <div>
        <img alt="Detail pages interface showing an object overview and related information" />
      </div>
    </div>
  </section>
</Container>

<Container>
  <section>
    <div>
      <div>
        <h3>Views</h3>

        <p>
          Save searches as Views and watch them update live with the chain.
        </p>

        <p>
          <a href="https://docs.rover.inc/core/views">Learn more</a>
        </p>
      </div>

      <div>
        <img alt="Views page showing saved searches that update live" />
      </div>
    </div>
  </section>
</Container>

<Container>
  <section>
    <div>
      <div>
        <h3>Labels</h3>

        <p>
          Add labels to addresses so key context is always at your fingertips, then use those labels to organize and filter on‑chain data across every workflow
        </p>

        <p>
          <a href="https://docs.rover.inc/core/labels-bookmarks">Learn more</a>
        </p>
      </div>

      <div>
        <img alt="Labels and bookmarks interface showing labeled addresses and saved items" />
      </div>
    </div>
  </section>
</Container>


# Start Guide
Source: https://docs.rover.inc/getting-started/start-guide

Get an overview of Rover's features and how to use them.

### Popular

<br />

<SimpleCardGrid>
  <SimpleCard href="/core/cmd-k" icon="command" title="Command Menu" description="Learn keyboard-driven navigation so you can move through Rover and run actions instantly." />

  <SimpleCard href="/core/tables" icon="table" title="Tables" description="See how to structure, filter, and sort on-chain data in tables tailored to your workflow." />

  <SimpleCard href="/core/views" icon="layer-group" title="Views" description="Create saved views to organize, filter, and share on-chain info for different workflows" />
</SimpleCardGrid>

***

### Rover basics

<br />

<SimpleCardGrid>
  <SimpleCard href="/core/detail-pages/transaction" icon="page" title="Transaction Detail Page" description="Inspect a single transaction, see what happened on‑chain, and jump into related addresses and assets" />

  <SimpleCard href="/core/detail-pages/address-detail-page" icon="page" title="Address Detail Page" description="Investigate an address or contract, understand its holdings, and follow its transaction history" />

  <SimpleCard href="/core/detail-pages/asset-detail-page" icon="page" title="Asset Detail Page" description="Explore a token or NFT, review its holders, and track recent on‑chain activity" />

  <SimpleCard href="/core/labels-bookmarks" icon="tag" title="Labels" description="Create labels to categorize on‑chain data so it’s easier to organize and filter across workflows" />

  <SimpleCard href="/core/bookmarks" icon="bookmark" title="Bookmarks" description="Bookmark important on‑chain items so you can quickly return to them and keep context in one place" />

  <SimpleCard href="/core/sharing" icon="arrow-up-from-bracket" title="Sharing" description="Share views and investigations with your team so everyone stays aligned in one unified platform" />
</SimpleCardGrid>


# Welcome
Source: https://docs.rover.inc/getting-started/welcome



Rover is a powerful engine for searching, monitoring, and aggregating on-chain data, all in one streamlined workspace. It helps teams track wallets, audit smart contracts, and debug transactions through an interface built for speed, precision, and real operational use.

<img alt="Home" />

With Rover, blockchain exploration becomes intuitive. It’s the first filter-based search engine for the blockchain, designed to answer complex questions instantly. Where traditional explorers show you raw data, Rover helps you find exactly what matters, fast. Every feature you’d expect from a block explorer is here, enhanced with real-time filtering and intelligent context that turn complex activity into actionable insights.

## Status & Data Coverage

In this beta release, Rover focuses on the Ethereum network. You’ll have access to three months of historical data, updated in real-time as new blocks are mined and finalized.

<Container>
  <div>
    <div>
      <div>
        <div>
          <div>
            <span>Name</span>
          </div>

          <div>
            <span>Search range</span>
          </div>

          <div>
            <span>Status</span>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <path />

              <path />

              <path />

              <path />

              <path />

              <path />
            </svg>

            <span>Ethereum</span>
          </div>

          <div>
            <span>October 2025 → Present</span>
          </div>

          <div>
            <span>Live</span>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <path />
            </svg>

            <span>Base</span>
          </div>

          <div>
            <span>Coming Soon</span>
          </div>

          <div>
            <span>-</span>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <path />
            </svg>

            <span>Tempo</span>
          </div>

          <div>
            <span>Coming Soon</span>
          </div>

          <div>
            <span>-</span>
          </div>
        </div>
      </div>
    </div>
  </div>
</Container>

***

## Learn more

<br />

<SimpleCardGrid>
  <SimpleCard href="/getting-started/start-guide" icon="book-open" title="Start Guide" description="Learn Rover’s core features and start answering real questions with on‑chain data" />

  <SimpleCard href="https://rover.instatus.com/" icon="sparkle" title="Status" description="Check the status of Rover at any time to be notified of system improvements or issues" />

  <SimpleCard href="https://cal.com/sophialatessa/onboarding-to-rover" icon="calendar" title="Book Live Demo" description="Schedule a live walkthrough tailored to your team’s on‑chain workflows" />
</SimpleCardGrid>