Transactions
This endpoint returns transactions for a given address across several EVM chains. By setting the ?decode parameter you can optionally choose to get both function calls and logs decoded.
The Transactions Endpoint allows for quick and accurate lookup of transactions associated with an address. Data is typically available within 100 ms after a block has been propagated to nodes.
Column Descriptions of the Transaction object
| Column | Description | Type |
|---|---|---|
| address | Wallet or ERC20 contract address | string |
| block_hash | Unique cryptographic block identifier. | string |
| block_number | Block’s sequential index. | string |
| block_time | Timestamp of block creation. | timestamp |
| block_version | Block’s protocol iteration. | integer |
| chain | Name of the blockchain | string |
| from | Address of sender | string |
| to | Address of receiver | string |
| data | Data of transaction | string |
| gas_price | Gas price of transaction as hexadecimal string | string |
| hash | Hash of transaction | string |
| index | Index of transaction | string |
| max_fee_per_gas | Max fee per gas of transaction as hexadecimal string | string |
| max_priority_fee_per_gas | Max priority fee per gas of transaction as hexadecimal string | string |
| nonce | Nonce of transaction as hexadecimal string | string |
| transaction_type | Type of transaction | string |
| value | Value of transaction as hexadecimal string | string |
Ordering
The data is ordered by descending block time, so that new transactions will always be delivered first.
Pagination
This endpoint is using cursor based pagination. You can use the limit 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.
next_offset to set the offset parameter of the next page of results. Using your own offset value will not have any effect.Headers
API key to access the service
Path Parameters
Wallet to get transactions for
Query Parameters
The offset to paginate through result sets. This is a cursor being passed from the previous response, only use what the backend has returned on previous responses.
Maximum number of transactions to return
x > 0Comma separated list of chain ids to get transactions for
Return only transactions with this method id
filter transactions to a given address
Return abi decoded transactions and logs
Response
Was this page helpful?