There are two sub-scenarios for this use case:
a user wants to inspect a deploy in a block
a user wants to inspect all deploys in a block
In both cases the user provides data (block hash at least, perhaps the deployId also) and is given the rholang execution trace that was produced for this block.
there is a way for a user to ask for a rholang execution trace for a given block (& optionally deployId)
this feature needs to be opt-in (flag)
this mechanism should not persist data, it’s strictly a read only mechanism
it seems that json is the obvious choice
rholang traces are a complicated topic and need to be investigated.
one piece that can be done fairly quick is to have the trace from rspace ( )