You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a contract calls other contracts, the events are all shown together in the Explorer view for the transaction.
Describe the solution you'd like
It would be helpful to users to see from which contract an event originates. This could be as simple as some kind of label on the div for each event shown. It could go next to the existing label, e.g. Contract log ∙ Print
becomes Contract log ∙ ST12YKQ22YZZF044Q1SW8W9A3BRZMCY2XSQ8YWBK8.liquidator-v1 ∙ Print
For example, looking at the above contract call, the print event number 9 comes from a different contract than the one originally called. This is not clear from this view.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a contract calls other contracts, the events are all shown together in the Explorer view for the transaction.
Describe the solution you'd like
It would be helpful to users to see from which contract an event originates. This could be as simple as some kind of label on the div for each event shown. It could go next to the existing label, e.g.
Contract log ∙ Print
becomes
Contract log ∙ ST12YKQ22YZZF044Q1SW8W9A3BRZMCY2XSQ8YWBK8.liquidator-v1 ∙ Print
or maybe it could be underneath of that label.
Additional context
Sample transaction here: https://explorer.hiro.so/txid/0xed26e882938b08989a7e701d640d67082f1e497c034289c780cae7fcaca27d35?chain=testnet
For example, looking at the above contract call, the print event number 9 comes from a different contract than the one originally called. This is not clear from this view.
The text was updated successfully, but these errors were encountered: