SonarX

Blockchain dataon Kafka

The processors that index a chain publish each normalized record to a Kafka topic as it is produced. You consume the topics with the client you already use, and the records carry the same column names and types as our warehouse tables, so a stream consumer and a SQL query describe the chain the same way.

Start trialContact us →

Stream mechanics

How the streams run

Record encoding
Avro or JSON
Latency
Seconds from tip

Streams feed trading and execution systems, transaction monitoring, and lakehouse loads that cannot wait for a batch cycle.

Live for chains like:

On the wire

What lands on the topics

A topic carries one dataset for one chain. The set of datasets on a given chain is configured per chain, and it is not the same everywhere: BSC, Polygon and Solana publish the full core set, while others publish the transfer and contract-creation subset. We confirm the exact dataset list for your chain before anything is signed.

  • Native, ERC-20, ERC-721 and ERC-1155 transfers, and contract creations.
  • Blocks, transactions, receipts, logs, traces and approvals on the chains configured for the full core set.
  • Solana account, instruction, stake and vote records on the Solana stream.
  • The same normalized column names and types as the corresponding datashare tables.
  • Per-record schemas published to a schema registry, so consumers can evolve without guesswork.

Access

How access works

  • One topic per chain and dataset. Which datasets a chain publishes is a per-chain setting, not a fixed list.
  • Credentials are issued per customer, and topic access is granted by prefix, so you only see the chains you buy.
  • Consumption is metered per customer, so usage is visible rather than estimated.
  • Records are produced by the same processors that write our warehouse tables, so the stream and the share agree.

Use cases

What teams build with it

  • Trading and execution systems that cannot wait for a batch cycle.
  • Transaction monitoring and fraud detection as activity happens.
  • Feeding an internal store or lakehouse continuously instead of on a nightly load.
  • Event-driven alerting on transfers, contract deployments or wallet activity.
  • Keeping a cache or index warm against chain tip.

Most teams pair a stream with a datashare: the topics carry the last few minutes, the share carries everything before that.

The rest of the platform

Other ways to get the data

Instant DatasharesFull chain history and real-time tables shared straight into your own data warehouse, or written to your bucket as files.Curated DatasetsCurated per-chain DeFi, staking, and tokens and payments datasets.BalancesPoint-in-time balance tables, a real-time balances API, and batch wallet-token-balance reads.Realtime APIBlocks, transactions, logs and traces over REST, plus low-latency node read and archive read endpoints.

Get started

Put a chain on your topics

Tell us the chains and the datasets you need. We will confirm what streams today, what can be enabled, and what it would take for anything else.

Start trialContact us →