Forks
List all forks
curl -X GET "https://example.com/v1/solidity/string/string/fork"{ "forks": [ { "createTime": "2019-08-24T14:15:22Z", "externalFork": { "chainConfig": { "debugEndpoint": "string", "endpoint": "string", "oklinkChainShortName": "string", "sourceFetcherApiKeys": [ "string" ], "sourceFetcherEndpoint": "string", "sourceFetcherTimeout": "string", "sourceFetcherType": "ETHERSCAN" }, "nodeAdditionalHeaders": "string" }, "extra": "string", "id": "string", "managedFork": { "chainId": "string", "parentBlockNumber": "string", "parentChainSpec": { "chainId": "string", "forkId": "string" }, "parentRpcEndpoint": "string", "rpcEndpoint": "string", "version": "string" }, "name": "string", "type": "MANAGED", "updateTime": "2019-08-24T14:15:22Z" } ]}Get trace by transaction GET
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)
Create a fork POST
Next Page