Add Your Chain

100% free

Blocktivity ranks blockchains by on-chain transaction activity. To be listed, your chain provides one stable API endpoint returning a daily transaction count, which we fetch hourly. We publish your number exactly as reported, with a visible data-status label showing how it was sourced.

Sources are submitted by the organisations that stand behind them: a block explorer, the chain's foundation or team, or a known website that serves chain data, community-run ones included. Your organisation's name is shown next to the chain's data, and you prove the submission is yours. If you are part of a chain's community, ask your explorer or foundation to submit it. Listing is free.

Submissions are reviewed manually. There's no automatic confirmation yet — if your chain is accepted, it will simply appear on the leaderboard.

Building the endpoint first? The full specification — every field, the exact JSON shape, and what each data-status requires — is at Listing spec.

Data-status you'll qualify for

Fill in the required fields to see the data-status you qualify for.

—

Who you are

The organisation that stands behind this source.

As it should appear on the coin page.

Your organisation's own site. Place the proof below on it, or on an account it owns.

Required

The minimum to be listed.

Self-Reported

Drives the coin URL: e.g. Bitcoin Cash → /coin/bitcoin-cash

Letters and numbers only. Used for display; the coin URL comes from the chain name.

Used for listing correspondence only. Not displayed publicly.

Your source

Must return JSON conforming to the tx-endpoint shape. Blocktivity fetches this hourly.

What this endpoint must return

Required

FieldTypeNotes
transactionsintegerTransaction count for the reported period, per the chain's disclosed txDefinition (required)
period_startstringISO 8601 UTC timestamp for the start of the counted period (required)
period_endstringISO 8601 UTC timestamp for the end of the counted period (required)
updated_atstringISO 8601 UTC timestamp when this response was last calculated. Blocktivity uses this for freshness checks. Must be within 24 hours of fetch time to avoid a stale status. (required)

Optional but strongly recommended

FieldTypeNotes
chainstringHuman-readable chain name (optional)
chain_idstringChain network identifier, e.g. mainnet (optional)
period"24h"Reporting period. Must be 24h — daily is the only supported period.
from_blockintegerFirst block included in the count (optional, aids auditability)
to_blockintegerLast block included in the count (optional, aids auditability)
transaction_definitionstringHuman-readable description of what is counted, e.g. successful user transactions only (optional)
failed_transactions_includedbooleanWhether failed transactions are included in the count (optional)
system_transactions_includedbooleanWhether system/protocol-internal transactions are included in the count (optional)

Worked example and the freshness rules: Listing spec → the tx-endpoint shape

Transaction definition

Blocktivity does not force a single definition — different chains count differently and that's fine. What we do require is disclosure. These 7 fields are shown on your coin page so visitors understand exactly what your number means.

What each of these means
FieldTypeNotes
successful"included" | "excluded"Are successful transactions counted?
included — Included in the count
excluded — Excluded from the count
failed"included" | "excluded"Are failed transactions counted?
included — Included in the count
excluded — Excluded from the count
system"included" | "excluded"Are system/protocol-internal transactions counted?
included — Included in the count
excluded — Excluded from the count
internal"included" | "excluded" | "n-a"Are internal (sub-call) transactions counted? Use n-a if the concept does not apply to this chain.
included — Included in the count
excluded — Excluded from the count
n-a — Not applicable to this chain
batched"as-batch" | "individually"Are batched transactions counted once (as-batch) or once per inner transaction (individually)?
as-batch — The batch counts as one transaction
individually — Each transaction in the batch counts
rollup"l2-user-tx" | "l1-settlement" | "both" | "n-a"For rollup chains: which layer is counted? Use n-a for non-rollup chains.
l2-user-tx — L2 user transactions
l1-settlement — L1 settlement transactions
both — Both L2 user and L1 settlement
n-a — Not applicable to this chain
window"utc-day" | "rolling-24h"Counting window: UTC calendar day (00:00–24:00 UTC) or rolling last 24 hours.
utc-day — UTC calendar day (00:00-24:00 UTC)
rolling-24h — Rolling last 24 hours

Full reference: Listing spec → Transaction-definition disclosure

Optional. Shown on your chain's public page, attributed to you. Plain language — exclusions, quirks, what counts as one transaction.

Authenticity proof — required

Prove the submission is your organisation's.

Your organisation's name goes next to the chain's data, so we check the submission is really yours. Place the token below where your proof method says, then submit: we check it before anything is listed. Full method reference: Listing spec → Authenticity verification.

By submitting you agree that Blocktivity may display your chain's transaction data with a visible source and data-status label.

Want more visibility? Rent the banner above the leaderboard, or become a sponsor to add a supporter badge next to your chain.