transactionBlocks
The transaction blocks that exist in the network.
scanLimit
restricts the number of candidate transactions scanned when gathering a page of
results. It is required for queries that apply more than two complex filters (on function,
kind, sender, recipient, input object, changed object, or ids), and can be at most
serviceConfig.maxScanLimit
.
When the scan limit is reached the page will be returned even if it has fewer than first
results when paginating forward (last
when paginating backwards). If there are more
transactions to scan, pageInfo.hasNextPage
(or pageInfo.hasPreviousPage
) will be set to
true
, and PageInfo.endCursor
(or PageInfo.startCursor
) will be set to the last
transaction that was scanned as opposed to the last (or first) transaction in the page.
Requesting the next (or previous) page after this cursor will resume the search, scanning
the next scanLimit
many transactions in the direction of pagination, and so on until all
transactions in the scanning range have been visited.
By default, the scanning range includes all transactions known to GraphQL, but it can be
restricted by the after
and before
cursors, and the beforeCheckpoint
,
afterCheckpoint
and atCheckpoint
filters.
transactionBlocks(
first: Int
after: String
last: Int
before: String
filter: TransactionBlockFilter
scanLimit: Int
): TransactionBlockConnection!