[Trace] debug_traceCall

The debug_traceCall allows tracing on a specific block if callArgs is provided.

JSONRPC: debug_traceCall

Request

application/json

Body

params

undefined[]

Array [

TracerCallObject

object

The tracer call object. See the next table for the object's properties.

from 20-byte DATA

(optional) Address the transaction is simulated to have been sent from. The 0x00..0 address is used if no address is specified.

to 20-byte DATA

(optional) Address the transaction is sent to.

input DATA

(optional) Hash of the method signature and encoded parameter. It replaces data field, but 'data` field is still supported for backward compatibility.

BlockNumberOrHashOrTag

object

oneOf

IntegerBlockNumber

the block number with type integer

number

HexadecimalBlockNumber

the block number with type hexadecimal

string

BlockTag

the block tag [latest, pending, earliest]

string

BlockHash

the block hash

string

TracerObject

object

Tracer type.

tracer string

Possible values: [4byteTracer, callTracer, fastCallTracer, evmdisTracer, noopTracer, opcountTracer, prestateTracer, revertTracer, unigramTracer, bigramTracer, trigramTracer]

Setting this will enable JavaScript-based transaction tracing, described in the next section. If set, the previous four arguments will be ignored. The predefined tracers can also be used as the following table.

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.

]

Responses

200

The detail tracing infomation

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

Example (from schema)

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

Loading...