Activity

View chronologically ordered transactions including native transfers, ERC20 movements, NFT transfers, and decoded contract interactions.

GET /v1/evm/activity/{address}

Get EVM activity for a given address

cURL

curl --request GET \
  --url https://api.sim.dune.com/v1/evm/activity/{address} \
  --header 'X-Sim-Api-Key: <x-sim-api-key>'

200

success

{
  "activity": [
    {
      "chain_id": 8453,
      "block_number": 26635101,
      "block_time": "2025-02-20T13:52:29+00:00",
      "tx_hash": "0x184544c8d67a0cbed0a3f04abe5f958b96635e8c743c070f70e24b1c06cd1aa6",
      "type": "receive",
      "asset_type": "erc20",
      "token_address": "0xf92e740ad181b13a484a886ed16aa6d32d71b19a",
      "from": "0xd152f549545093347a162dce210e7293f1452150",
      "value": "123069652500000000000",
      "value_usd": 0.14017463965013963,
      "token_metadata": {
        "symbol": "ENT",
        "decimals": 18,
        "price_usd": 0.001138986230989314,
        "pool_size": 5.2274054439382835
      }
    }
  ],
  "next_offset": "KgAAAAAAAAAweDQ4ZDAwNGE2YzE3NWRiMzMxZTk5YmVhZjY0NDIzYjMwOTgzNTdhZTdAVxVC-y0GAAUhAAAAAAAA6XCRAQAAAAAAAAAAAAAAAD0AAAAAAAAAAAAAAAAAAAA"
}

The Activity API provides a realtime feed of onchain activity for any EVM address. The newest activity is returned first and includes the following activity types:

• send - Outgoing transfers of tokens or native assets
• receive - Incoming transfers of tokens or native assets
• mint - Token minting activities
• burn - Token burning activities
• swap - Token swaps and exchanges
• approve - Token approval transactions
• call - Generic contract interactions that don’t fall into the above categories

Each activity includes detailed information such as:

• Native token transfers
• ERC20 token transfers with metadata (symbol, decimals)
• ERC721 (NFT) transfers with token IDs
• Contract interactions with decoded function calls

Activities are mostly indexed events. There are, of course, no events for native token transfers (wen 7708?). We do have a heuristic to catch very simple native token transfers, where the native token transfer is the entirety of the transaction, but unfortunately we don’t currently catch native token transfers that happen within internal txns.

Data Finality & Re-orgs

Sim APIs are designed to automatically detect and handle blockchain re-organizations. We detect any potentially broken parent-child block relationships as soon as they arise and update our internal state to match the onchain state, typically within a few hundred milliseconds. This re-org handling is an automatic, non-configurable feature designed to provide the most reliable data.

Warnings

When requesting activity for specific chains using the chain_ids parameter, the API may return warnings if some requested chain IDs are not supported. Unlike errors, warnings indicate non-fatal issues where the request can still be partially fulfilled.

When unsupported chain IDs are included in your request, the API will:

• Return activity for all supported chains you requested
• Include a warnings array in the response with details about the unsupported chains

Example: Request with Unsupported Chain IDs

If you request ?chain_ids=1,9999,10, the API returns activity for chains 1 and 10 (supported), and includes a warning about chain 9999 (unsupported):

{
  "activity": [
    {
      "chain_id": 1,
      "block_number": 18500000,
      "block_time": "2025-02-20T13:52:29+00:00",
      "tx_hash": "0x184544c8d67a0cbed0a3f04abe5f958b96635e8c743c070f70e24b1c06cd1aa6",
      "type": "receive",
      "asset_type": "erc20",
      "token_address": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
      "from": "0xd152f549545093347a162dce210e7293f1452150",
      "value": "1000000",
      "value_usd": 1.0,
      "token_metadata": {
        "symbol": "USDC",
        "decimals": 6,
        "price_usd": 1.0
      }
    }
  ],
  "warnings": [
    {
      "code": "UNSUPPORTED_CHAIN_IDS",
      "message": "Some requested chain_ids are not supported. Activity is returned only for supported chains.",
      "chain_ids": [9999],
      "docs_url": "https://docs.sim.dune.com/evm/supported-chains"
    }
  ]
}

Check the Supported Chains page to see which chains are currently supported for the Activity endpoint.

Filtering

You can filter activities server-side using the following query parameters:

• token_address — Filter by token contract address. Accepts a single address or a comma-separated list. For example, pass the USDC contract address to return only USDC-related activity, or pass multiple addresses to match any of them. Note: swap and call activities do not have a single token address, so they are always excluded when this filter is set. Native transfers are also excluded since they have no token contract.
• activity_type — Filter by activity type. Accepts a single value or a comma-separated list. Accepted values: send, receive, mint, burn, swap, approve, call.
• asset_type — Filter by asset standard. Accepts a single value or a comma-separated list. Accepted values: native, erc20, erc721, erc1155. Use native to include native token transfers (e.g. ETH). Contract call activities have no asset type and are excluded when this filter is set.

All filters are optional and can be combined. For example, to get only native token receives:

GET /v1/evm/activity/{address}?activity_type=receive&asset_type=native

To get only sends and receives (multi-value):

GET /v1/evm/activity/{address}?activity_type=send,receive

Or to get only USDC sends:

GET /v1/evm/activity/{address}?token_address=0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48&activity_type=send

For additional client-side filtering, we include all the data needed in the responses. See our Token Filtering guide for more details.

Compute Unit Cost

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

Headers

X-Sim-Api-Key · string · required

Used for authenticating requests. Visit Authentication to learn how to create your API key.

Path Parameters

address · string · default: 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 · required

Wallet address to get activity for

Query Parameters

chain_ids · string

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 activity from chains with the default tag. See the Supported Chains Tags section.

offset · string

The offset to paginate through result sets. This is a cursor being passed from the previous response, only use what the backend returns here.

limit · integer<int64> · default: 20

Maximum number of activity items to return. Default is 20 when not provided. Values above 100 are reduced to 100.

Required range: 1 <= x <= 100

token_address · string

Filter activities by token contract address. Provide a single address (e.g. ?token_address=0xa0b8...) or a comma-separated list (e.g. ?token_address=0xa0b8...,0xdac1...). Only activities involving the specified token(s) will be returned. Swap and call activities are excluded when this filter is set, as they do not have a single token address. Native transfers are also excluded since they have no token contract.

activity_type · string

Filter activities by type. Provide a single value (e.g. ?activity_type=send) or a comma-separated list (e.g. ?activity_type=send,receive). Only activities matching one of the specified types will be returned.

asset_type · string

Filter activities by asset standard. Provide a single value (e.g. ?asset_type=native) or a comma-separated list (e.g. ?asset_type=erc20,erc721). Use native to include native token transfers (e.g. ETH). Contract call activities have no asset type and are excluded when this filter is set.

Response

200

application/json

Successful Response

activity · object[] · required

Array of activity items

Show child attributes

warnings · object[]

Array of warnings that occurred during request processing. Warnings indicate non-fatal issues (e.g., unsupported chain IDs) where the request can still be partially fulfilled.

Show child attributes

next_offset · string

Pagination cursor for the next page of results