# End-2-End Traces

End-to-end (E2E) traces track an operation's journey through the entire decentralized application architecture. Starting from the frontend data source, E2E tracing assigns a unique span ID to each captured event. These spans document every step and invocation, creating a cohesive, long trace. This trace effectively maps the operation's path through various [data sources](/concepts/data-sources.md), enabling clear visibility into the performance and potential bottlenecks within the system's workflow.

When your [dApp frontend](/concepts/data-sources/react-frontends.md) is added as datasource to blocktorch through [installing Dragon SDK](/concepts/data-sources/react-frontends.md#installation), each successful user interaction triggered in your dApps's frontend leading to a transaction on the blockchain will show up as a full trace in your [log details](/use-cases/searching/logs/log-details.md).


---

# 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.blocktorch.xyz/use-cases/tracing/end-2-end-traces.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.