> For the complete documentation index, see [llms.txt](https://docs.blocktorch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocktorch.xyz/use-cases/tracing/end-2-end-traces.md).

# 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).