Error messages displayed in the overview of a failed transaction are now more consistent, making it easier for you to understand the failure reason.
You can now see three types of errors:
- EVM-level error
- Error reason in the case the execution was reverted
- Error message that points to problems in your code
Improved Transaction Trace
From the call trace, it was previously unclear which contract was calling a function and where the function resided. We’ve removed this ambiguity with a recent update. Now, when one contract calls another contract, this is noted as:
(caller => receiver).functionName(inputs)
This change makes it easier to determine the original contract (caller) and the receiver contract for every single trace call.
Use Tenderly Node Extensions to build custom RPC endpoints that fit your dapp without changing its existing logic. Optimize dapp performance, improve user experience, and get greater control and flexibility both on-chain and during development.
Try Tenderly Node ExtensionsSubscribe to Tenderly product updates
