Hedera Data: Index EVM Contracts and Token Activity

Index Hedera's smart contract events, HTS token activity, and decoded transactions in one pipeline, delivered to your own database. Real-time and complete historical data, no node to run.

Hedera is an enterprise-grade public network chosen by many of the world's leading institutions to bring real-world assets, payments, and identity onchain. It runs on hashgraph, an asynchronous Byzantine fault tolerant consensus algorithm, and is governed by the Hedera Council, a term-limited group of global organizations rather than a single foundation. On top of that base, Hedera exposes the Hedera Smart Contract Service, an EVM-equivalent execution environment you reach through a standard JSON-RPC relay, alongside the native Hedera Token Service (HTS) for minting and moving tokens. The native cryptocurrency is HBAR, and fees are priced in fixed USD. You can read how the team frames it at hedera.com.

That enterprise footprint is the data problem. Tokenized securities, stablecoins, FX collateral, and DeFi settle across Hedera's EVM contracts and HTS tokens, and each block emits contract events, token transfers, and decoded calls that a downstream product needs in a queryable shape. The consensus layer is hashgraph rather than a typical chain, but the smart-contract and token data is standard EVM output. Indexing Co covers Hedera in a single pipeline, decodes the raw chain into the shape you want, and delivers it to your own PostgreSQL, warehouse, or webhook. Real-time and full history, with no node to operate.

Source Hedera EVM blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why Hedera data is hard

Hashgraph, Not a Typical Chain Hedera reaches finality through hashgraph consensus rather than proof-of-work or a standard proof-of-stake fork, so the network internals differ from a vanilla EVM chain. The smart-contract output is still standard EVM logs and traces, but you want an indexer that reads that layer correctly instead of assuming a familiar block structure.

EVM Contracts Plus Native HTS Tokens Assets on Hedera live in two places: contracts on the Hedera Smart Contract Service and tokens issued through the native Hedera Token Service. A complete dataset has to cover both surfaces, tie HTS token movements to the contracts that touch them, and keep the two views consistent.

Enterprise and RWA Workloads Tokenized securities, stablecoins, and FX collateral posted by institutions demand audit-grade completeness. Missing a transfer or lagging behind the network head is not acceptable when the data backs regulated real-world assets and reconciliation, so backfill and real-time delivery both have to be exact.

Your Own DB, Not a Hosted API Generic RPC endpoints and hosted query APIs leave you rate-limited and renting someone else's schema. Powering an enterprise app or analytics workload on Hedera means owning the data in your own store, shaped the way your product queries it.

What Indexing Co delivers for Hedera

The DIY Path

Stand up and maintain the whole stack yourself.

Run a Hedera node or wire up a JSON-RPC relay endpoint.
Fetch and decode logs, traces, and receipts against the right ABIs.
Reconcile HTS token activity with Smart Contract Service events by hand.
Build backfill, finality handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers Hedera to your store.

Hedera contract events, HTS token activity, and decoded txs in a single pipeline.
Decoded data, shaped by your JavaScript transform.
Lands in your PostgreSQL, BigQuery, warehouse, or webhook.
Real-time delivery plus complete backfilled history. No node, no relay to babysit.

What you can index

EVM data type	On Hedera, for example
Contract events and logs	DeFi swaps, lending events, RWA settlement calls
Token transfers (HTS, ERC-20, ERC-721)	Stablecoin payments, tokenized securities transfers
Decoded transactions and traces	Smart Contract Service calls, account operations
Protocol and account state	Vault balances, token supplies, tokenized-asset registries

A transform, not a subgraph

You write the transform in JavaScript, not AssemblyScript, and change it without re-indexing from block zero. Indexing Co runs your function over each block server-side: decode the logs you care about and return rows for your destination.

// Indexing Co transform: reshape each block into rows for your database
function transform(block) {
  const results = [];
  const signatures = [
    'event Transfer(address indexed from, address indexed to, uint256 value)'
  ];

  for (const tx of block.transactions || []) {
    for (const log of tx.receipt?.logs || []) {
      const event = utils.evmDecodeLogWithMetadata(log, signatures);
      if (!event) continue;
      results.push({
        chain: block._network,
        block: Number(block.number),
        tx_hash: tx.hash,
        contract_address: log.address?.toLowerCase(),
        from: event.decoded.from,
        to: event.decoded.to,
        value: event.decoded.value,
      });
    }
  }
  return results;
}

Hedera with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a Hedera node or relay, decode every protocol's ABIs, reconcile HTS tokens, and build backfill and finality handling in-house.

Use Indexing Co if

You want Hedera contract events, HTS token activity, and decoded transactions delivered to your own database, with real-time plus complete history and no infrastructure to run.

Get a Demo Open the Console

FAQ

Do I need to run a Hedera node?

No. Indexing Co sources Hedera blocks, logs, and traces for you, including full historical data, so you never operate a node or babysit a JSON-RPC relay endpoint.

Does Indexing Co support Hedera's EVM and native token services?

Yes. Because the Hedera Smart Contract Service is EVM-equivalent, contract events decode exactly like any EVM chain, and the pipeline captures Hedera Token Service (HTS) transfers alongside them.

Can I index any contract or token on Hedera?

Yes. Point a pipeline at any Hedera contract or set of tokens, from DeFi protocols to tokenized real-world assets and stablecoins, and we decode the events against the right ABI.

Where does the Hedera data go?

Into your own destination: PostgreSQL, BigQuery, a warehouse, or a webhook. You define the output schema and own the storage.

Can I get complete historical Hedera data?

Yes. We backfill from your chosen start block and merge it with real-time data, so your Hedera dataset is gap-free from your start point forward.

Get Started

Index Hedera in minutes. Set up your first Hedera contract or token pipeline without running a node.