Get trace by transaction
API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID. The results looks very similar to the normal [Ethereum call trace](https://media.githubusercontent.com/media/sentioxyz/docs/HEAD/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace. This allows you to build chart that marks the order of fund flow. %20(1)%20(1)%20(1).png)
In: header
Path Parameters
Query Parameters
Fetch the decoded trace, which will give you the function info, decoded parameters of both external and internal call trace.
Disable optimizations to make internal calls more accurate, but gas costs will differ from the actual execution.
Only effective when disableOptimizer=true.
Response Body
application/json
curl -X GET "https://example.com/v1/solidity/string/string/string/transaction/string/call_trace"{ "contentType": "string", "data": "string", "extensions": [ { "@type": "string", "property1": null, "property2": null } ]}Run bundle simulation POST
You could also create bundle simulations so that one transaction could be executed one after another. For `blockNumber` `transactionIndex` `networkId` `stateOverrides` and `blockOverrides` fields, only the first simulation takes effect.
Query Table By Name GET
Query table schema by name.