# Searchbar

In searchbar you can find everything you need by applying a special filter. Please, click the button to expand the full list of available filters

<figure><img src="/files/o8FD1Hrq9YsPwwBEiYNv" alt=""><figcaption><p>Full list of filters</p></figcaption></figure>

Follow the prompts in the input field to find what you need :relaxed:&#x20;

## Find your transaction by tx ID

Choose appropriate filter and paste TxID. Please note that:

1. KLY native tx id is 256-bit BLAKE3 hash
2. KLY-EVM tx id is 256-bit 0x-prefixed SHA3 hash

For example:

<figure><img src="/files/8610WBjrkovXiyopN0Lr" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/oeFCgglbIyZzJUaIpWsr" alt=""><figcaption></figcaption></figure>

The same works for EVM transactions. Get the txid from your wallet or web3 SDK and paste to explorer

<figure><img src="/files/UAqIFHFnPO3Ql4mZvZV2" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/3GLzVvAbnYexjpm1kbGo" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Note that there are 2 types of transactions shown here - the transaction is running in parallel mode and not in parallel. **Klyntar has full parallel support - parallel WASM VM, parallel EVM, etc.**
{% endhint %}

## Find block by shard index&#x20;

Each shard works as independent linear blockchain. So, to find the first block on shard or, saying 1337th block on shard choose filter and paste required input

Find the first block on shard 0 (indexation starts from 0)

<figure><img src="/files/7NOtNY1NNzhmJ9ObRktB" alt=""><figcaption></figcaption></figure>

Result

<figure><img src="/files/WdQEmaa8T37SxQzLhWQS" alt=""><figcaption></figcaption></figure>

Find the block 1337th on shard 0

<figure><img src="/files/P9mFtPZ8xD9iGCFNBEKE" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/HkygfdoX31qyi7yVkMHd" alt=""><figcaption></figcaption></figure>

## Find block by ID

Also, each block has own ID. This ID consists of 3 parts:

1. Epoch Index
2. Creator-pool pubkey (currently Ed25519), Base58 encoded
3. Block index in own sequence

In each epoch on each shard there is a timeframe for each validator to generate blocks. Each validator starts own sequence of indexation.

For example, if:

1. Epoch index = 455
2. Set of validators for shard X - V0, V1, V2

The IDs of blocks will be:

1. 455:V0:107 - 107th block by pool V0 on epoch 455
2. 455:V1:37 - 37th block by pool V1 on epoch 455
3. 455:V2:10 - 10th block by pool V2 on epoch 455

So, choose filter, paste ID and search

<figure><img src="/files/ZValPcKK7ydDwzKeMHAm" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/5oiIDKdVx2COBFEl7XMA" alt=""><figcaption></figcaption></figure>

If you click \`Check AFP\` you will be able to see the AFP - aggregated finalization proof created by quorum majority. If block has this proof - it's a signal that it was approved and included to blockchain

<figure><img src="/files/zg0BZObwZQFcXPUuXGNX" alt=""><figcaption></figcaption></figure>

AFP presented in a raw form but your node and developers will know what to do with it

<figure><img src="/files/x2tQCDod0fNIlgbsZzuz" alt=""><figcaption></figcaption></figure>

## Find staking pool(validator) by ID

Pool has appropriate pubkey and the full ID of pool will be pubkey + `(POOL)` postfix

For example, go to searchbar and try to find:

<figure><img src="/files/IwHcQO2Pea53NiF1Vd48" alt=""><figcaption></figcaption></figure>

You will be redirected here

<figure><img src="/files/QS9N4aQZpN1jTagZLmTg" alt=""><figcaption></figcaption></figure>

## Find epoch data by ID

The easiest - just pase index of epoch and find required data

<figure><img src="/files/L3isjiGmaqGw51yQzCJg" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/dJ4rKSllFkhyc1ykRzj7" alt=""><figcaption></figcaption></figure>

## Find account info by ID

There are 2 types of accounts in KLY network - **user**(EOA - externally owned account) and **contract.**

Due to the sharded nature of our network, when searching for an account (user or contract) you should specify a prefix with the shard ID.

For example:

1. User account vlad on shard\_0 has ID - **shard\_0:vlad**
2. Contract **blablabla** on shard\_5 has ID - **shard\_5:blablabla**

Examples

## Find user account by ID

<figure><img src="/files/DzKTe7yyde6XN6nWIquK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Lr9nxKGqvXiLcU3xNEaV" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/9U16VhHUirvNskuLrc4P" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qxM0C43nquRY4QlPHgVv" alt=""><figcaption></figcaption></figure>

### Find EVM user account

<figure><img src="/files/rmPlHVIanyexbFFJ7dFp" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/SEWN002uoimmvm8xAFah" alt=""><figcaption></figcaption></figure>

## Find KLY-WVM contract account

<figure><img src="/files/uQE34GEsjLLi74K440To" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/6BzoIXpSEt1oFBfSP0ux" alt=""><figcaption></figcaption></figure>

### Find KLY-EVM contract account

<figure><img src="/files/gOh2MTScye3UhkV4lGED" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/oWPNxrmZcCAnJhN0IAVQ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.klyntar.org/build-core-and-join-network/explorers-and-how-to-use-them/usage-guide/searchbar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.