# Query detail

> Inspect any query — view the exact dialect-correct SQL Flax compiled and the raw result rows returned by your warehouse.

*[View this page in the Flax docs](https://flax-analytics.com/docs/exploring/query-detail)*

Query detail is the transparency window into Explore. It shows exactly what Flax
compiled and ran, so you can verify a metric, debug an unexpected number, or copy
the SQL for use elsewhere.

## What it shows

For any query you can inspect two things:

- **Compiled SQL** — the dialect-correct statement Flax generated from your field,
  filter, sort, and limit selections, including the joins and row-access filters it
  applied. This is the exact text sent to your warehouse.
- **Raw results** — the rows the warehouse returned, before any chart formatting or
  spreadsheet layer.

Seeing both side by side makes it easy to confirm that a measure aggregates what
you expect and that governance rules were applied.

## Why inspect a query

- **Trust** — verify that a headline number comes from the SQL you think it does.
- **Debugging** — when a result looks off, read the compiled SQL to find the cause,
  such as an unexpected join or filter.
- **Learning** — see how point-and-click selections map onto SQL, which helps when
  you move to the [SQL runner](/docs/exploring/sql-runner).

## Related concepts

How selections become SQL is covered in depth under
[SQL compilation](/docs/modeling/sql-compilation), and the rules that shape the
`WHERE` clause live in [row-access filters](/docs/modeling/row-access-filters).

## Next steps

- [The SQL runner](/docs/exploring/sql-runner)
- [SQL compilation](/docs/modeling/sql-compilation)
- [Drill-down](/docs/exploring/drill-down)