Start free
AboutMarketplacePricingContactSearch apps
Products
VantageStrataFolioGroundProof
Use cases
Treasury and financePayments and fintechTrading and market makingFunds and researchIssuers and protocolsCompliance and riskResearch and media
Sign inStart free
Dashboard · VantagePlanned

Smart Contract Deployments by Chain: New Contracts per Day

How many new smart contracts are deployed on each chain per day?

New contracts per day on each chain, counted apart for EVM contracts, Solana programs and Move packages, with deployers and factory share.

Build it in Studio →Ask for this data
ShareEmail itvoltfincrypto.com/apps/smart-contract-deployments-by-chain
Blueprint

What the dashboard will show.

The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.

  • Chain
  • Period

Overview

New EVM contracts, Solana programs and Move packages, with the accounts that deployed them.

EVM contracts, latest day

count

Contracts created on the covered EVM chains on the latest complete UTC day, from create and create2 calls in traces.

Figurechain_activity_dailyAwaiting data

Solana programs, latest day

count

New programs deployed on Solana on the latest complete day, through the upgradeable loader and loader-v4.

Figurechain_activity_dailyAwaiting data

Move packages, latest day

count

Packages published on Sui and on Aptos on the latest complete day, shown per chain.

Figurechain_activity_dailyAwaiting data

Distinct deployers, latest day

count

Accounts that signed at least one deployment on the latest complete day, following factory calls back to the signer.

Figurechain_activity_dailyAwaiting data

New EVM contracts by chain

count

Contracts created each day over the selected period on each covered EVM chain, stacked by chain.

Stacked barschain_activity_dailyAwaiting data

By chain

Factory share, upgrades, first-time deployers and each chain's own figures.

Factory share

%

EVM contracts created by other contracts rather than directly by accounts, as a share of the latest day's EVM deployments.

Figureaddress_labelsAwaiting data

Upgrades, latest day

count

Solana program upgrades and Sui and Aptos package upgrades on the latest complete day, counted apart from new deployments.

Figurechain_activity_dailyAwaiting data

First-time deployers

count

Accounts that deployed a contract for the first time on a given chain on the latest complete day.

Figurechain_activity_dailyAwaiting data

Top 10 deployers' share

%

The share of the latest day's EVM deployments signed by the ten most active deploying accounts.

Figurechain_activity_dailyAwaiting data

Deployments by chain

Each covered chain with its deployments, distinct deployers, factory share and upgrades over the last 30 days, under the rule that fits its virtual machine.

Tablechain_activity_dailyAwaiting data

Chain
Every covered chain
Period
Last 30 days, 90 days or a year
About

What it answers, and for whom.

Every new smart contract is created on-chain by a transaction, so deployments are a measure of building that anyone can check. This dashboard counts them on each covered chain per day: EVM contracts from creation calls, Solana programs, Sui and Aptos packages, NEAR contracts and new TON contracts, along with how many distinct accounts deployed them and how many came from factories.

Deployments do not compare across virtual machines: a Solana program serves many users, while an EVM chain deploys a contract for every token, pool or smart wallet. So each chain is read against its own history, and the share created by factories and launchpads is shown apart from deployments by developers. Every count links to the transactions behind it.

Method

How it will be measured.

Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.

How receipts work →
  1. A deployment is counted once, on the day its creating transaction succeeded: create and create2 calls in EVM traces, new programs on Solana, published packages on Sui and Aptos, DeployContract actions on NEAR and new contracts on TON.
  2. Counts are never added across virtual machines, since a Solana program, a Move package and an EVM contract are different units; EVM chains are summed only with each other.
  3. Factory share is the part of EVM contracts created by another contract rather than by an account directly; launchpads, DEXs and wallet factories can create them in large numbers, so the share sets automated deployments apart.
  4. Distinct deployers are the accounts that signed each day's deployments, found by following factory calls back to the signer, and every figure carries a receipt with the block and transaction.

The data it needs

Read from chain state and history

  • chain_activity_dailyTo buildChain activity by dayTransactions, active sending addresses, new addresses, contracts created and gas used on each chain per day, counted from blocks and transactions.
  • address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
  • EVM chains: create and create2 calls in execution traces, with the creator and whether it is a contract
  • Solana: upgradeable loader DeployWithMaxDataLen and Upgrade instructions, and loader-v4 deployments
  • Sui: Publish and Upgrade commands in programmable transaction blocks; Aptos: code::publish_package_txn calls
  • NEAR: DeployContract actions; TON: messages carrying a state_init that deploy a new contract
  • Factory, launchpad and wallet factory labels, recorded with their source
Questions

Questions people ask.

Do contract deployments measure developer activity?

Partly. A deployment is a verifiable on-chain act, but one team can deploy many contracts, and factories such as token launchpads create contracts automatically. The dashboard separates factory deployments and counts distinct deployers, which says more about how many builders are active than raw counts do.

Why are Solana programs counted differently from EVM contracts?

On Solana, code lives in programs that many users share, and a new token needs no new program: it is an account of the existing token program. EVM chains deploy a contract for each token or smart wallet. Solana's program count therefore runs far lower for the same activity, so each chain is read against its own history.

What is a factory contract?

A contract that creates other contracts, such as a DEX creating a pool for each new pair, a launchpad creating each token or a wallet factory creating each smart account. The factory share tile shows how much of each day's EVM deployments come from them.

Are contract upgrades counted as deployments?

No. Upgrading a Solana program or a Sui or Aptos package changes code at an existing address, so those upgrades are counted on their own. On EVM chains a new implementation behind a proxy is a new contract and counts as a deployment, while repointing the proxy does not.

Which chains are covered?

EVM chains including Ethereum, Base, Arbitrum, BNB Chain, Polygon, Avalanche, Monad, Sonic, Berachain, HyperEVM and Plasma, plus Solana, Sui, Aptos, NEAR and TON, each counted under the rule that fits its virtual machine. More chains are added as their traces are built.

create2
The EVM operation that deploys a contract at an address computed in advance from the deployer, a salt and the code.
Factory
A contract whose job is to deploy other contracts, such as pools, tokens or smart accounts.
Program
Solana's name for deployed code; programs hold no state of their own and serve every account that uses them.
Package
A published bundle of Move modules on Sui or Aptos, the unit of deployment on those chains.
Related
All Layer 1 chains apps →

Build Smart Contract Deployments by Chain: New Contracts per Day on verified data.

Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.

Start free →Open live apps