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

# Trade explorer

The venue's entire activity, open to anyone who cares to look.

The trade explorer captures everything the venue does: each fill, each market's live state, each parameter and each change made to it, all built from chain events and linked back to them. You can open it without a wallet, since nothing in it belongs privately to anyone. This is where "transparently on-chain" either gets verified or turns out to mean nothing.

## Per market

| Panel          | Contents                                                                                                                    |
| -------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Live quote     | Current bid, ask and mid with the complete breakdown, priced exactly as the router would price it right now                 |
| Regime         | The active regime, the signals behind it (feed timestamp, stream market status), and how long it has been in force          |
| Inventory      | The vault's mix relative to target and band, along with skew direction and size                                             |
| Parameters     | Tier, spreads, clip, caps and band, all read directly from `ParamController`                                                |
| History        | Fills with itemised breakdowns, spread revenue by regime, and the halt log with reasons                                     |
| Listing record | The tier evidence, the bytecode review result, the issuer disclosure, and proof-of-reserve status where a feed is available |

## Venue-wide

* Volume, number of fills and revenue, split by market, by venue (vault or RFQ) and by regime.
* A single figure for total vault inventory exposed to Robinhood Assets (Jersey) Ltd, as described in [Issuer risk](/risk/issuer.md).
* The [execution quality](/transparency/execution-quality.md) dataset: how far each fill landed from the oracle mid, aggregated and available to download.
* The governance log: each parameter proposal, past and pending, with its reasoning, timelock window and execution.

## Every number links to its source

Every figure links to the Blockscout event, transaction or contract read it came from. The explorer is built on the open-source indexer, so anyone can run it against any RPC and compare the results; if the explorer and the chain ever disagree, the chain is right and the difference is a bug to report.

## For auditors and integrators

All of the data shown here can be pulled raw from the [API](/architecture/api.md) at `/v1/markets`, `/v1/fills` and `/v1/execution-quality`, or downloaded as CSV, with full per-position LP histories for account holders. Researchers are free to use it. Our view is that an RWA market which no one can independently reconstruct does not really have a record at all.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iridius.xyz/using-iridius/trade-explorer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.