Skip to main content
Activity Sv 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.

​
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 activity will be returned only for the supported chains. For example, if you request chain_ids=1,9999,10,77777777777: 
{
  "activity": [
    // Activity for chains 1 and 10 only
  ],
  "warnings": [
    {
      "code": "UNSUPPORTED_CHAIN_IDS",
      "message": "Some requested chain_ids are not supported. Activity is 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.

​
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.

​
Token Filtering

We include all the data needed for custom filtering in the responses, allowing you to implement your own filtering logic. For a detailed explanation of our approach, see our Token Filtering guide.

​
Compute Unit Cost

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