We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
similar to ethtx.info, we want to see what contracts are called and the decoded calldata in the execution transaction of the proposal
The text was updated successfully, but these errors were encountered:
to save the hassle of formatting, a potential workaround is just linking to the tenderly simulation (assuming it's possible to have a public link to a custom sim) since they show something similar, e.g. see the trace in the random transaction: https://dashboard.tenderly.co/tx/mainnet/0x162eea3804ea9e47a27e44b741e6ddfe899af606bf9df80faee89127cf2d19df
Sorry, something went wrong.
No branches or pull requests
similar to ethtx.info, we want to see what contracts are called and the decoded calldata in the execution transaction of the proposal
The text was updated successfully, but these errors were encountered: