/search/transactions
allows the caller to search for transactions that meet certain conditions. Some conditions include matching a transaction hash, containing an operation with a certain status, or containing an operation that affects a certain account. /search/transactions
is considered an "indexer" endpoint and Rosetta implementations are not required to complete it to adhere to the Rosetta spec. However, any Rosetta "indexer" MUST support this endpoint.
The network_identifier specifies which network a particular object is associated with.
Operator is used by query-related endpoints to determine how to apply conditions. If this field is not populated, the default and
value will be used.
max_block is the largest block index to consider when searching for transactions. If this field is not populated, the current block is considered the max_block. If you do not specify a max_block, it is possible a newly synced block will interfere with paginated transaction queries (as the offset could become invalid with newly added rows).
5
offset is the offset into the query result to start returning transactions. If any search conditions are changed, the query offset will change and you must restart your search iteration.
5
limit is the maximum number of transactions to return in one call. The implementation may return <= limit transactions.
5
The transaction_identifier uniquely identifies a transaction in a particular network and block or in the mempool.
The account_identifier uniquely identifies an account within a network. All fields in the account_identifier are utilized to determine this uniqueness (including the metadata field, if populated).
CoinIdentifier uniquely identifies a Coin.
Currency is composed of a canonical Symbol and Decimals. This Decimals value is used to convert an Amount.Value from atomic units (Satoshis) to standard units (Bitcoins).
status is the network-specific operation type.
"reverted"
type is the network-specific operation type.
"transfer"
address is AccountIdentifier.Address. This is used to get all transactions related to an AccountIdentifier.Address, regardless of SubAccountIdentifier.
"0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347"
success is a synthetic condition populated by parsing network-specific operation statuses (using the mapping provided in /network/options
).
Expected response to a valid request
transactions is an array of BlockTransactions sorted by most recent BlockIdentifier (meaning that transactions in recent blocks appear first). If there are many transactions for a particular search, transactions may not contain all matching transactions. It is up to the caller to paginate these transactions using the max_block field.
total_count is the number of results for a given search. Callers typically use this value to concurrently fetch results by offset or to display a virtual page number associated with results.
5
next_offset is the next offset to use when paginating through transaction results. If this field is not populated, there are no more transactions to query.
5