> For the complete documentation index, see [llms.txt](https://docs.r.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.r.xyz/glider-ide/usage.md).

# Usage

This page describes how to use Glider interface and its features

{% hint style="info" %}
Note that in case the query is run against a whole blockchain the results will be grouped by uniques bytecodes, thus while checking a contract address, one should also check for similar contracts in etherscan to get full list of duplicate addresses.
{% endhint %}

### Basic usage

<figure><img src="https://2237101709-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDX4Ojc4j1ef51TUAtYOx%2Fuploads%2FWbyu2zqQv2WhEHFXRwj6%2Fspaces_vNCyQODNfxkMFwdzKHsZ_uploads_ndHgGKRRGgDJ818bYBXa_image.webp?alt=media&amp;token=d9f77af4-9d38-4562-bfdd-db6f9c378563" alt=""><figcaption><p>Sample Query Code</p></figcaption></figure>

In general, Glider provides with a REPL-like interface. On the left side, the query code is written; on the right side, the output is shown.&#x20;

* To run the query, the researcher needs to press the `Run` button.
* The `Chain` dropdown list is used to select the blockchain on which to run the query.
* The `Execute` clause is used to filter the recent contracts or to run on a full list. This feature is still in development.
* The `Profiler` checkbox is used to show line-by-line profiling information of the execution; this is useful to do benchmarks, reveal bottlenecks and optimize the query code.