Back to blogs
Written by
Patrick Collins
Published on
March 3, 2024

How to Get All the Transactions From a Contract Address

In this tutorial, you will learn several techniques for querying and retrieving all transactions from a contract address.

Table of Contents

If you don’t know where to start, getting all the transactions of a smart contract address can be cumbersome and time-consuming. In this tutorial, you will learn several techniques for querying and retrieving all transactions from a contract address.

We’ll look into getting smart contracts transactions manually, using centralized services such as Etherscan or Dune Analytics, and even building your own solutions using popular SDKs and libraries powered by companies like Alchemy (Alchemy SDK), and Quicknode.

If you're new to all of this, checkout our solidity smart contract development course on Cyfrin Updraft, completely for free.

Let’s get started!

How to fetch all the transactions from a smart contract address

Querying a node directly for all transactions in a smart contract address is difficult due to the way the blockchain stores data but a key skill to learn for web3 developers. Blockchains like Ethereum aren’t relational databases themselves and are not designed for easy querying. They are a string of blocks connected to each other, a sort of linked list.

Because of this, if all you have is a node, you would need to “brute force” go through each block, gather a list of all transactions, and check if the transaction originates or is sent to the address you are looking for. Additionally, you’d need an archive node - an instance of an Ethereum client configured to build an archive of all historical states.

Luckily though, lots of services out there have already built optimized solutions storing and indexing these transactions in databases ready for you to be queried.

We will look at each example to query transactions from a smart contract address as well as get notified when a new transaction happens.

We’ve put together a GitHub repo with all the examples for you to explore!

Why retrieving all the transactions from a contract address is important?

There are cases where smart contract auditors and security researchers need this information to learn more about protocols:

  • Does a protocol have a history of silently upgrading features without telling the community?
  • How can you see what contracts are connected to each other?
  • Want to find exactly when an exploit was executed?

Others where web3 dapps developers need to show this information to their users, or where DeX need this information to perform certain actions on their platforms.

Regardless of the use case, fetching historical and current transactions from a Smart Contract address is helpful whenever you’re dealing with Blockchain data.

Let’s get started!

Get started fetching all the transactions from a smart contract address

For our example, we will use the Ethereum Mainnet Aave token, as it’s a proxy contract and we can also show some event querying aspects like “how many times it’s been upgraded by governance.”

First, let’s learn how we would fetch blockchain transactions to and from a smart contract if we were to do it manually - brute force.

1. Brute Force - Query the blockchain to get a smart contract address transactions

As said before, fetching Smart Contract transactions directly querying the blockchain is definitely the most time-consuming of all the solutions we’ll explore in this article - but also the most eye-opening when it comes to understanding how transactions work.

Here is an example of brute force getting transactions with and one using ethers.js - two of the most popular web3 libraries to date.

Let’s start by adding a start block and end block, to avoid making a bazillion calls to your node.

const { ethers } = require("ethers"); 

const START_BLOCK = 17950195; 
const END_BLOCK = 17950197;

async function getAllTransactionsForContract(){
  const provider = new ethers.providers.JsonRpcProvider(process.env.RPC_URL); 
  for (let blockNumber = START_BLOCK; blockNumber < END_BLOCK; blockNumber++){ 
    const block = await provider.getBlock(blockNumber); 
    const transactions = block.transactions 
      for (const transaction of transactions){ 

With we can do the same:

import os 
from web3 import Web3 
START_BLOCK = 17950195 
END_BLOCK = 17950197 

def main(): 
  w3 = Web3(Web3.HTTPProvider(os.getenv("RPC_URL"))) 
  for block in range(START_BLOCK, END_BLOCK): 
    block = w3.eth.get_block(block, full_transactions=True) 
      for transaction in block.transactions: 
if __name__ == "__main__": 

As we can see above, the “brute force” method involves going block-by-block transaction-by-transaction until you find all the events you’re looking for, which can take a very long time.

And here is the worst part this list is non-exhaustive! If your address is a contract, contracts can make transactions to and from each other in a single transaction but will not be the main “to” or “from”. Let’s see why:

Contract-to-contract getting smart contract transactions

First, let’s quickly refresh how the transaction object will look like

  "Transaction": {
    "hash": "example_hash_value", // DataHexString< 32 >: The transaction hash, keccak256 of the serialized RLP encoded representation of transaction.
    "to": "example_address_to", // Address: The address transaction is to.
    "from": "example_address_from", // Address: The address transaction is from.
    "nonce": 12345, // number: The nonce for transaction ensuring order and non-replayability.
    "gasLimit": "example_big_number", // BigNumber: Gas limit for transaction, refunded if unused or consumed if insufficient.
    "gasPrice": null, // null | BigNumber: Price per unit of gas for transaction, null for EIP-1559 transactions.
    "maxFeePerGas": "example_big_number", // BigNumber: Maximum price per unit of gas, null for non-EIP-1559 transactions.
    "maxPriorityFeePerGas": "example_big_number", // BigNumber: Priority fee price per unit of gas, null for non-EIP-1559 transactions.
    "data": "example_data", // BytesLike: Data for transaction, represents call data in a contract.
    "value": "example_big_number", // BigNumber: Value in wei for transaction.
    "chainId": 1, // number: Chain ID for transaction, used in EIP-155 to prevent replay attacks.
    "r": "example_r_value", // DataHexString< 32 >: The r portion of the elliptic curve signatures for transaction.
    "s": "example_s_value", // DataHexString< 32 >: The s portion of the elliptic curve signatures for transaction.
    "v": 27 // number: The v portion of the elliptic curve signatures, refines x-coordinate points and encodes chain ID in EIP-155.

As we can see we have a “From” and a “To” fields containing the address where the Tx originates, and where it ends - we’re interested in every transaction that contains our contract address in the To or From fields.

Here’s the issue:

Let’s say that a Wallet interacts with a contract’s function “doStuff()”, we’ll call it contract A. In that case, the “from” field will be the Wallet’s address, and the “To” field will be our contract address - awesome!

Now, let’s say that in the doStuff() function, the contract will be interacting with another contract, called “contract B” - in that case "from" and "to" will still just be A & B even though we interacted with C.

The code above would miss this contract-to-contract call! And we would miss a transaction.

To get all of those transactions, you’d have to simulate each transaction running something like debug_traceTransaction keep track of the stack, and keep track of which opcodes interact with other contracts.

It’s a pretty laborious and time-intensive process and, ultimately, using the code above would only give us a subset of all the Smart contract transactions.

You could write all this, but most op to go with indexing transactions into an easier-to-query database or use a service that makes it more accessible.

Get all the transactions from a contract address - Centralised Services

Luckily there are services out there that are making our job of retrieving all transactions in a smart contract or address way easier. Let’s explore them, and understand the trade-offs.

get all ethereum transactions from a wallet or contract using etherscan

An example of internal transactions from etherscan

One of the easiest ways to get a list of transactions (and internal transactions) is to use a block explorer like etherscan.

For our Aave token, seeing a list of transactions is very easy. If we select internal and toggle on Advanced we can see a list of contracts that have interacted with Etherscan.

On Etherscan’s back end, they are indexing all this data for us to “see” it more easily.

They also have an advanced filtered mode, but unfortunately, we would still lack some granularity, and getting exactly the transaction info we want can be a little tricky.

Let’s see how Dune Analytics, partly, solves this.

2. Get a smart contract transactions using Dune Analytics

Get all transactions from a contract or wallet using dune analytics

Dune Analytics is a platform that allows users to create, share, and explore Ethereum data dashboards. It provides insights into by allowing users to query and visualize data in a user-friendly manner.

Simply put, it indexes blockchain “stuff” so that you can query it as if it’s a SQL database. For example, we can easily see all transactions in our Aave Token.

First, if you haven’t already, let’s navigate to Dune analytics and create a new account.

Then, navigate to the “Queries” tab and click on the “New query” button.

This will open up a console-like editor, where you’ll be able to write SQL queries in it.

Copy and paste the following code in the text editor and click “Run”:

FROM ethereum.traces
  "from" = 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9
  or "to" = 0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9

After a few seconds, you should see all the transactions appearing in the table below - more than 345,000!

Dune comes with a table known as ethereum.traces, which includes all the transactions in a contract. The query above will find EVERY transaction that interacted with the Aave token or the Aave token interacted. Saving you the hurdle of having to simulate every transaction as we had to before with our Brute force method! ADD ANCHOR

Now, this is great if you want a quick way to visualize all the transactions from and to a Smart Contract or wallet address. You can also implement it in your code using the Dune API - but what if we want even more granularity and flexibility?

In that case, we might want to use something like the Alchemy SDK or the Quicknode SDK

4. Alchemy

In this case, we’re going to use the popular Alchemy SDK - which offers a set of methods and APIS to allow us to fetch Blockchain data with ease.

One of these is the Alchemy Transfer API that allows you to easily fetch historical transactions for any address across Ethereum and supported L2s including Polygon, Arbitrum, and Optimism.

The getAssetTransfers method does in fact something similar to what we’ve done before using Dune Analytics - Plus it will give you some extra granularity over the data you want to fetch - like External transactions vs. Internal, or filter them by contract standard.

To get all transactions from and to our Aave token smart contract you can copy the following code:

// Setup: npm install alchemy-sdk
import { Alchemy, Network } from "alchemy-sdk";

const config = {
  apiKey: "demo",
  network: Network.ETH_MAINNET,
const alchemy = new Alchemy(config);

// Aave token on ETH Mainnet
const aaveTokenAddress = "0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9";

const res = await alchemy.core.getAssetTransfers({
  fromBlock: "17950195",
  toAddress: toAddress,


This will print a list of ALL the transactions from Block 0 to the latest available block - in a few milliseconds!

BTW, For this, you can also use the Python SDK Patrick Collins made to make it easier to work with the Alchemy API in Python, here’s an example:

import os
from alchemy_sdk_py import Alchemy

MY_ADDRESS = "0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9"  

def main():
    alchemy = Alchemy(network=CHAIN_ID)
    transfers = alchemy.get_asset_transfers(to_address=MY_ADDRESS)
    # this is a paginated version, we could add  `get_all_flag=True` but we'd make a LOT of API calls!

if __name__ == "__main__":

5. QuickNode SDK

QuickNode SDK - offers various modules, each having methods that make fetching blockchain data easier than getting the raw data and having to filter them manually.

One of the modules, called the API module, lets you make GraphQL queries leveraging the QuickNode Graph API to make intended queries and get only the valuable data. Right now, it is supported on Ethereum and Polygon, while core RPC functions in SDK are supported on all EVM chains.

The events.getByContract query returns the events for a smart contract provided the contract address; the query can be formatted to filter transactions based on block number, wallet address, type, etc. The response is paginated, making it easier to navigate larger payloads.

To get all transactions from and to our Aave token smart contract, you can copy the following code:

// Setup: npm install @quicknode/sdk
import API from "@quicknode/sdk/api";

const qn = new QuickNode.API({
    contractAddress: '0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9', // Aave token on ETH Mainnet
    filter: {
      blockNumber: {
        gte: 1
      type: {
        in: ['TRANSFER'],
  .then((response) => console.log(response));

This will print a list of ALL the transactions from Block number greater than or equal to 1 to the latest available block (in a paginated format) - in a few milliseconds!

Congratulations! You've just learned how to get all the transactions from a contract address!


In this guide on how to get all the transactions from a smart contract or wallet address, you've learned everything you need to know to retrieve the information you need from any on-chain activity. If you want to get more in depth and learn web3 development, make sure to checkout our smart contract development and auditing courses on Cyfrin Udpraft, completely for free!

Secure your protocol today

Join some of the biggest protocols and companies in creating a better internet. Our security researchers will help you throughout the whole process.
Stay on the bleeding edge of security
Carefully crafted, short smart contract security tips and news freshly delivered every week.