Decoded transactions
Enable decoded transaction data and logs by adding the?decode=true query parameter to your request.
When decoding is enabled, two types of data may be decoded:
- Transaction call data: The
datafield of each transaction may include an additionaldecodedobject at the root level of the transaction, representing the parsed function call. - Event logs: When a transaction contains EVM logs, each log may include an additional
decodedobject representing the parsed event.
Pagination
This endpoint is using cursor based pagination. You can use thelimit parameter to define the maximum page size.
Results might at times be less than the maximum page size.
The next_offset value is included in the initial response and can be utilized to fetch the next page of results by passing it as the offset query parameter in the next request.
Compute Unit Cost
The Transactions endpoint has a fixed CU cost of 1 per request. See the Compute Units page for detailed information.Headers
Used for authenticating requests. Provide an API key with a purpose of Sim API. See Authentication.
Path Parameters
EVM wallet address
Query Parameters
Filter by chain(s). Accepts numeric chain IDs and/or tags. Provide a single value (e.g. ?chain_ids=1 or ?chain_ids=mainnet) or a comma-separated list (e.g. ?chain_ids=1,8543,testnet). Chain names are not accepted. If this query parameter is omitted, results include transactions from chains with the default tag. See the Supported Chains Tags section.
Maximum number of results to return. Default is 100 when not provided. Values above 100 are reduced to 100.
1 <= x <= 100The offset to paginate through result sets. This is a cursor being passed from the previous response, only use what the backend returns here.
When true, it includes decoded transaction logs in the response. Accepts only boolean values true or false. You can also omit this parameter to disable decoding. Invalid values will return an error.