Skip to main content
Takes exactly the same body as POST /query and returns one JSON object. Use it for exploring and debugging; for real workloads use /query, which is 2–2.5× smaller and therefore cheaper. See Arrow vs JSON.

​
Example

(Shortened: the second transaction is left out.)

​
Response

​
integer
First block covered.
​
integer
Last block covered.
​
integer
fromBlock for the next page.
​
integer
Total rows in the response.
​
integer
The chain head at query time.
​
integer | null
The newest final block at query time.
​
string | null
Hash of to_block when it’s above finalized_block; otherwise null.
​
string
The prepared query id of this request’s filter.
​
string[]
Selected fields this chain doesn’t have.
​
object[]
Present when transactions were requested. Keys are the snake_case column names.
​
object[]
Present when logs were requested.
​
object[]
Present when blocks were requested.
Values: numbers for integer fields, 0x hex strings for binary fields, decimal strings for amounts, arrays and objects for nested fields, null for missing. See The JSON format.

​
Limits

  • At most 100,000 rows per response; maxObjects is lowered to that. Like Arrow pages, one block may push a page past it.
  • The whole response is built before it’s sent.