[Trace] debug_traceChain

Returns the structured logs created during the execution of EVM between two blocks (excluding start) as a JSON object. This endpoint must be invoked via debug_subscribe as follows:

NOTE: Don't trace too many blocks at the same time as it can overuse machine resources.

JSONRPC: debug_traceChain

Request

application/json

Body

params

object[]

Array [

anyOf

StartBlockNumber

Tracing start block number.

integer

EndBlockNumber

Tracing end block number.

integer

TracingOptions

disableStorage boolean

Setting this to true will disable storage capture in the null (structLog) tracer (default: false).

disableMemory boolean

Setting this to true will disable memory capture in the null (structLog) tracer (default: false).

disableStack boolean

Setting this to true will disable stack capture in the null (structLog) tracer (default: false).

timeout string

Overrides the default timeout of 5 seconds for trace-enabled EVM execution. A duration string can be anything that is accepted by Go time.ParseDuration function such as "10s" or "300ms".

tracer string

Possible values: [null, 4byteTracer, callTracer, fastCallTracer, evmdisTracer, noopTracer, opcountTracer, prestateTracer, revertTracer, unigramTracer, bigramTracer, trigramTracer, custom javascript tracer code]

If this field is empty or null, then the structLog tracer is used where the execution of every opcode is shown in detail. This null tracer is extremely heavy and usually too verbose for any debugging purpose, so it is advised to use other predefined tracers. This field can be the name of one of the predefined tracers shown below.

Tracer Name	Description
4byteTracer	traces 4-byte solidity function signatures.
callTracer	a slow version of fastCallTracer. It is deprecated in favor of fastCallTracer.
fastCallTracer	traces internal contract calls, gas usage, and call results.
evmdisTracer	returns information needed to perform evmdis-style disassembly.
noopTracer	is a template tracer that does nothing.
opcountTracer	is a sample tracer that counts the executed opcode.
prestateTracer	returns information needed to construct a custom local genesis state that this transaction can run on.
revertTracer	returns the revert reason, or an empty string if the transaction has not reverted.
unigramTracer	counts the occurrence of each opcode.
bigramTracer	counts the occurrence of two consecutive opcodes.
trigramTracer	counts the occurrence of three consecutive opcodes.

Otherwise this field is interpreted as a piece of javascript code. You can find more about custom JS tracer here and here. Below is an example custom tracer that prints the gasUsed after each opcode "{gasUsed: [], step: function(log) { this.gasUsed.push(log.getGas()); }, result: function() { return this.gasUsed; }, fault: function() {}}". Note that some nodes with --rpc.unsafe-debug.disable option will prohibit custom tracer.

]

Responses

200

Returns the structured logs created during the execution of EVM between two blocks as a JSON object.

application/json

Schema

Schema

error

object

code int64required

A Number that indicates the error type that occurred. This MUST be an integer.

code	message	description
-32700	Parse error	invalid JSON was received by the server. An error occurred on the server while parsing the JSON text.
-32602	Invalid params	Invalid method parameter(s).

message string

A String providing a short description of the error. The message SHOULD be limited to a concise single sentence.

data string

A Primitive or Structured value that contains additional information about the error. This may be omitted. The value of this member is defined by the Server (e.g. detailed error information, nested errors etc.).

result object

Returns the structured logs created during the execution of EVM between two blocks as a JSON object.

Example (from schema)

{
  "jsonrpc": "2.0",
  "id": 0,
  "error": {
    "code": -32700,
    "message": "Parse error",
    "data": "string"
  },
  "result": {}
}

Loading...