BSC
POST
GET
addToGroupcompileSerpentdebug_accountRangedebug_batchSendRawTransactiondebug_getBadBlocksdebug_metricsdebug_standardTraceBadBlockToFiledebug_standardTraceBlockToFiledebug_storageRangeAtdebug_traceBlockdebug_traceBlockByHashdebug_traceBlockByNumberdebug_traceTransactioneth_getBlockReceiptseth_getWorketh_sendTransactioneth_submitHashrateeth_submitWorkgetFilterChangesgetHexgetMessagesgetStringhasIdentitynewFilternewGroupnewIdentitypostputHexputStringuninstallFilterversion
Last updated on January 1, 1970
1 min read
Method debug_standardTraceBlockToFile undefined ()
connect with JSON-RPC protocol
debug_standardTraceBlockToFile
Method not allowed
Generates files containing the block trace. A separate file is generatedfor each transaction in the block.You can also specify a trace file for a specific transaction in a block.Use debug_standardTraceBadBlockToFile to view the trace for an invalidblock.
Parameters
blockHash - data
Block hash.
txHash - data
The transaction hash. Optional. If omitted, then a trace file is generated for each transaction in the block.
Request
curl --location --request POST 'https://bsc.getblock.io/mainnet/'
--header 'x-api-key: YOUR-API-KEY'
--header 'Content-Type: application/json'
--data-raw '{"jsonrpc": "2.0",
"method": "debug_standardTraceBlockToFile",
"params": ["0x0cf46846c9f2abef8e40ed2f8deea4b789464f44284efe25d443e8d272393fce", null],
"id": "getblock.io"}'
Response
{
"result": "null",
"id": "getblock.io",
"status_code": 405,
"message": "Method not allowed"
}
Start Building with GetBlock RPCs for Free
Previous
{ "overview": "Overview", "guides": "Guides", "get-started": "Get Started", "rpc-service": "Nodes Methods", "getblock-explorer": "Explorer API", "getblock-tracker": "Tracker API", "nodes-endpoints": "Nodes Endpoints" }
Next
{ "overview": "Overview", "guides": "Guides", "get-started": "Get Started", "rpc-service": "Nodes Methods", "getblock-explorer": "Explorer API", "getblock-tracker": "Tracker API", "nodes-endpoints": "Nodes Endpoints" }
