Indexed Polkadot Asset HubBlockchain Data
Polkadot Asset Hub is a system parachain, separate from the Polkadot relay chain, where fungible tokens, stablecoins and NFTs are issued and held, with its own blocks and its own state secured by the relay chain.
How to query Polkadot Asset Hub data with SonarX
Instant Data Share
Available todaySnowflake, and file dumps to your object storage
Query Polkadot Asset Hub blockchain data with plain SQL from a live database inside your own Snowflake account, populated with the indexed chain dataset. There is no pipeline to build and no second copy to store. The same dataset ships as file dumps to your own object storage for lakes and warehouses that are not Snowflake.
- Full history as a Snowflake data-share
- File dumps to S3 or your own object storage
- Real-time delivery, current to chain tip — on request
Used for:
- Analytics teams already on Snowflake that want Polkadot Asset Hub data beside their existing tables
- Fund accounting and treasury reporting that reconciles against a fixed history
- Cross-chain questions answered in one SQL statement instead of one query per chain
- Loading Polkadot Asset Hub history into BigQuery, Databricks, Redshift or a Spark lake
- Replacing a self-hosted indexer and the engineering time that keeps it running
- Serving one governed dataset to several desks without copying it per team
Realtime API
Enabled on requestREST over the indexed dataset
Query indexed Polkadot Asset Hub records over REST, reading the same dataset the share reads, with no warehouse in the path.
Used for:
- Applications that need one answer rather than a table scan
- Customer-facing screens where query latency is visible to a user
- Services that have no data warehouse and do not want to run one
- Prototyping against production data before committing to a share
- Backend checks that run per request instead of per batch
- Teams that want indexed Polkadot Asset Hub data behind their own API layer
Polkadot Asset Hub data: frequently asked questions
What is Polkadot Asset Hub?
Polkadot Asset Hub is a system parachain: a chain run as part of the Polkadot network for a job the network itself needs, rather than for an independent application. Its job is assets. Fungible tokens, including the stablecoins issued on Polkadot, are created and held here, along with NFTs, and transfers of those assets happen here. Asset Hub is a separate chain from the Polkadot relay chain, with its own blocks, its own runtime and its own state. The relay chain provides its security and finality, while the assets and the accounts that hold them live on Asset Hub. DOT is the native token, accounts are SS58-encoded, and the chain launched under the name Statemint before it was renamed.
Polkadot Asset Hub data on SonarX
SonarX indexes Asset Hub blocks, extrinsics and the events the runtime emits, and asset transfers priced and netted by account, covering DOT and the tokens issued on the chain. Each amount carries its asset’s own decimals. Asset Hub is indexed as its own network and is never folded into the relay chain dataset, so a question about issued assets reads from Asset Hub directly.
Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.
How SonarX indexes Polkadot Asset Hub
Asset Hub runs its own runtime, so its blocks are decoded against Asset Hub metadata, version by version, and not against the relay chain’s. Assets are identified by asset ID rather than by contract address, and the same SS58 account can hold DOT and several issued assets at once, each with different decimals. SonarX resolves every transfer to its asset and its decimals before pricing it, so DOT and a stablecoin moved in the same block land as separate, correctly scaled rows.
What teams build with Polkadot Asset Hub data
Stablecoin and token flow analysis is the first workload: issuance, transfers and holder concentration for the assets issued on Polkadot. Holdings reporting is the second, for funds and custodians that hold DOT or issued assets on Asset Hub and need an independent record. Cross-chain reconciliation is the third, matching what an account holds on Asset Hub against what it holds on the relay chain, which needs both datasets side by side. Tokens and payments covers asset activity across chains.
Getting Polkadot Asset Hub data from SonarX
Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Asset Hub history is available now, and real-time delivery is provisioned on request. Say whether the relay chain is in scope too, since it is a separate dataset. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.
Is Polkadot Asset Hub the same as Polkadot?
No. Asset Hub is a separate chain with its own blocks, extrinsics, events and state. It is a system parachain that relies on the Polkadot relay chain for security, but asset issuance, asset transfers and NFTs happen on Asset Hub, not on the relay chain. SonarX indexes the two as separate networks with separate datasets.
What Polkadot Asset Hub data does SonarX index?
SonarX indexes Asset Hub blocks, extrinsics and the events the runtime emits, and asset transfers priced and netted by account, covering DOT and the tokens issued on Asset Hub, such as stablecoins. Amounts are carried with each asset's own decimals so they read in the units holders see.
How do I get Polkadot Asset Hub data into Snowflake?
SonarX provisions a data-share into your own Snowflake account. The share appears as a database you query with SQL, so there is no pipeline to build and no second copy to store, and it stays current as SonarX advances the indexing pipeline.
Why does Asset Hub data need its own decoder?
Because Asset Hub has its own runtime. Extrinsics and events are decoded against the metadata of the runtime active at each block, and Asset Hub upgrades its runtime separately from the relay chain. A decoder built for relay-chain blocks does not read Asset Hub blocks, and an asset is identified by its asset ID on Asset Hub, not by a contract address.
Was Polkadot Asset Hub previously called Statemint?
Yes. The chain launched under the name Statemint and was later renamed Polkadot Asset Hub. It is the same network with the same history, so SonarX coverage runs across both names.
