CONX (formerly XPLA) Data: Index EVM Contract Activity

Index CONX's EVM contract events, token transfers, and decoded transactions in one pipeline, delivered to your own database. CONX was formerly XPLA. Real-time and full historical data, no node to run.

CONX, formerly XPLA, is a Cosmos SDK Layer 1 that started out as a blockchain for games and content. In November 2025 a governance proposal renamed the token, its symbol, and the chain's brand identity from XPLA to CONX, and the team now frames the network around connecting culture and finance: stablecoin payments and remittances, real-world asset tokenization, and rewards for original creators. The chain runs native Cosmos modules and CometBFT consensus, with an EVM module so Solidity contracts and Ethereum tooling work alongside them. CONX is the token that pays for gas and secures the validator set. You can read how the team frames it at conx.xyz.

Be clear about where the activity is. Most CONX transactions today run through the chain's native Cosmos side, and the EVM layer is quiet by comparison. If your contracts live on the EVM side, Indexing Co covers it 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 CONX EVM blocks

Ingest blocks, logs, traces

Decode ABIs to events

Transform your JavaScript

Deliver your database

Why CONX data is hard

A Rebrand Mid-History The chain was XPLA until November 2025 and is CONX now. Tickers, explorers, and older docs still use both names, so a dataset that spans the change has to treat them as one network and keep contract identity stable across the rename.

Cosmos SDK Plus an EVM CONX is a Cosmos SDK chain with an EVM module, so EVM contract activity lands in the Ethereum-compatible environment while most of the chain's traffic runs through native Cosmos modules and CometBFT consensus. Reading the EVM side correctly means treating it as an EVM, not guessing at a bespoke format.

Decoding Per Contract Every token, NFT collection, or payment contract you track on the EVM side needs its own ABI and event handling, and proxies make the right ABI a moving target.

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 app or analytics workload on CONX means owning the data in your own store, shaped the way your product queries it.

What Indexing Co delivers for CONX

The DIY Path

Stand up and maintain the whole stack yourself.

Run a CONX archive node or wire up a third-party RPC.
Fetch and decode EVM logs, traces, and receipts against the right ABIs.
Track proxy upgrades and per-contract event schemas by hand.
Build backfill, reorg handling, and real-time delivery from scratch.

Indexing Co

One pipeline sources, decodes, and delivers CONX EVM data to your store.

CONX EVM contract events, token transfers, 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 RPC babysitting.

What you can index

EVM data type	On CONX, for example
Contract events and logs	Events emitted by EVM contracts you deploy or track
Token transfers (ERC-20, ERC-721)	ERC-20 token payments, NFT mints and transfers
Decoded transactions and traces	EVM contract calls and value flows
Protocol and account state	Token balances and NFT ownership rebuilt from events

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;
}

CONX with Indexing Co

Run it yourself if

You want full control of node infrastructure and have the team to operate a CONX archive node, decode every contract's ABIs, and build backfill and reorg handling in-house.

Use Indexing Co if

You want CONX EVM contract events, token transfers, 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

Is CONX the same chain as XPLA?

Yes. CONX is the new name for XPLA, adopted through a governance proposal that passed in November 2025. The token, its symbol, and the chain's brand moved to CONX; history from the XPLA era is the same chain.

Do I need to run a CONX node?

No. Indexing Co sources CONX EVM blocks, logs, and traces for you, including full historical data, so you never operate an archive node or babysit an RPC endpoint.

Does Indexing Co cover the Cosmos side of CONX?

No. The pipeline reads the EVM layer. Native Cosmos transactions that never touch the EVM, which is where most CONX activity happens today, are out of scope.

Can I index any CONX EVM contract?

Yes. Point a pipeline at any CONX EVM contract or set of contracts, from tokens and NFT collections to your own deployments, and we decode the events against the right ABI.

Does Indexing Co handle CONX reorgs and proxy upgrades?

Yes. The pipeline accounts for chain reorganizations and tracks proxy implementation changes so your decoded data stays correct as contracts upgrade.

Where does the CONX 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 CONX data?

Yes. We backfill from your chosen start block, including the XPLA era, and merge it with real-time data, so your CONX dataset is gap-free from your start point forward if you want it.

Get Started

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