> For the complete documentation index, see [llms.txt](https://docs.nebra.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nebra.one/developer-guide/proof-explorer.md).

# Proof explorer

View the verification status of your proofs on [NEBRA's proof explorer](https://www.nebrascan.io/).

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

The proof explorer landing page displays information about the latest verified batches as well as statistics such as the total number of proofs/batches that UPA has verified so far, and how many proofs are pending.\
\
To view the status of all the proofs submitted for your circuit, enter your circuit ID into the search bar on the top right.<br>

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

This will bring you to a page listing the status of each proof for this circuit, which is either:

* `VERIFIED` - The proof is valid and has been aggregated into a verified batch on-chain.
* `PENDING` - The proof has not been aggregated yet and may be either accepted or rejected.
* `REJECTED` - The proof was invalid.

<figure><img src="/files/QQzzGvszhX8CFcdyilRF" alt=""><figcaption><p>Verified proofs</p></figcaption></figure>

<figure><img src="/files/Z3WEejQlS8rooqphD3EL" alt=""><figcaption><p>Rejected proofs</p></figcaption></figure>

Click on the "Proof ID" links here or enter a proof ID in the search bar to see more information about an individual proof such as its corresponding public inputs.

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.nebra.one/developer-guide/proof-explorer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.