# 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](https://docs.blocktorch.xyz/concepts/data-sources), enabling clear visibility into the performance and potential bottlenecks within the system's workflow.

When your [dApp frontend](https://docs.blocktorch.xyz/concepts/data-sources/react-frontends) is added as datasource to blocktorch through [installing Dragon SDK](https://docs.blocktorch.xyz/concepts/data-sources/react-frontends#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](https://docs.blocktorch.xyz/use-cases/searching/logs/log-details).