Transactions

Retrieve granular transaction details including block information, gas data, transaction types, and raw transaction values.

The Transactions API allows for quick and accurate lookup of transactions associated with an address. Transactions are ordered by descending block time, so the most recent transactions appear first.

Unsupported Chain IDs

When you request chain IDs that are not supported, the API will return a warning in the response instead of throwing an error. The warnings field will contain information about which chain IDs were not supported, and transactions will be returned only for the supported chains.

For example, if you request chain_ids=1,9999,10,77777777777:

{
  "wallet_address": "0x37305b1cd40574e4c5ce33f8e8306be057fd7341",
  "transactions": [
    // Transactions for chains 1 and 10 only
  ],
  "warnings": [
    {
      "code": "UNSUPPORTED_CHAIN_IDS",
      "message": "Some requested chain_ids are not supported. Transactions are returned only for supported chains.",
      "chain_ids": [9999, 77777777777],
      "docs_url": "https://docs.sim.dune.com/evm/supported-chains"
    }
  ]
}

Invalid chain ID tags (like typos in tag names) will still return errors as designed. Only invalid numeric chain IDs generate warnings.

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:

1. Transaction call data: The data field of each transaction may include an additional decoded object at the root level of the transaction, representing the parsed function call.
2. Event logs: When a transaction contains EVM logs, each log may include an additional decoded object representing the parsed event.

For more details, see the response information below.

Decoding is only available for contracts that exist on Dune.com. Search for your contract on Dune to check if it’s available for decoding. Transactions without logs, logs without known signatures, or contracts not indexed on Dune will not include decoded data.

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.

You can only use the value from next_offset to set the offset parameter of the next page of results. Using your own offset value will not have any effect.

Compute Unit Cost

The Transactions endpoint has a fixed CU cost of 1 per request. See the Compute Units page for detailed information.