In smart-contract platforms such as Ethereum, a call trace is a step-by-step record of every call made while a single transaction executes. A user's transaction may call one smart contract, which calls a second contract, which moves tokens through a third; the trace lists each of these nested calls in order, with the caller, the target, the function and arguments, any value sent, the return data or error, and the gas used.
Traces are not stored in blocks. Nodes produce them on request by re-executing the transaction, for example through tracing methods in the JSON-RPC interface of clients such as Geth. Block explorers use traces to show internal transactions, the ether transfers made by contracts rather than by accounts. Developers read them in a debugger or tools such as Hardhat to find why a call reverted, while auditors and incident teams use them to reconstruct exploits.
Ref 1070001313