Skip to main content

​
Overview

The Hedera mainnet (short for main network) is where applications are run in production, with transaction fees paid in HBAR. Any application or retail user can submit transactions to the Hedera mainnet; they’re automatically consensus-timestamped and fairly ordered. Any Hedera account can query data associated with Hedera’s services and stored on-chain. Every transaction requires payment as a transaction fee denominated in tinybars (100,000,000 tℏ = 1 ℏ). You can learn more about transaction fees and estimate your application costs here. If you’re looking to test your application (or just experiment), please visit Testnet Access. The Hedera testnet enables developers to prototype and test applications in a simulated mainnet environment that uses test HBAR for paying transaction fees.
Transaction Throttles Transactions on the Hedera Mainnet are currently throttled. You will receive a "BUSY" response if the number of transactions submitted to the network exceeds the threshold value.

​
Main Network Throttles

Network Request TypesThrottle (tps)
Cryptocurrency Transactions

AccountCreateTransaction: 2 tps

TransferTransaction (inc. tokens): 10,000 tps
Other: 10,000 tps

Consensus Transactions

TopicCreateTransaction: 5 tps

Other: 10,000 tps

Token Transactions

TokenMintTransaction:

  • 125 TPS for fungible mint
  • 50 TPS for NFT mint

TokenAssociateTransaction: 100 tps
TransferTransaction (inc. tokens): 10,000 tps

Other: 3,000 tps

Schedule TransactionsScheduleSignTransaction: 100 tps
ScheduleCreateTransaction: 100 tps
File Transactions10 tps
Smart Contract TransactionsContractExecuteTransaction: 15 million gas per second
ContractCreateTransaction: 15 million gas per second
Queries (per node)

AccountBalanceQuery: 1000 tps

ContractGetInfo: 700 tps
ContractGetBytecode: 700 tps
ContractCallLocal: 700 tps

FileGetInfo: 700 tps
FileGetContents: 700 tps

Other: 10,000 tps

Receiptsunlimited (no throttle)

​
High-Volume Throttles

In addition to the standard throttles above, the network provides dedicated high-volume throttle capacity for entity creation transactions that set high_volume = true. These throttles run in parallel — they do not consume capacity from the standard system, and the standard system does not consume capacity from them.
Throttle BucketTransaction TypesCapacity
HighVolumeCryptoThrottlesCryptoCreate, ScheduleCreateSet by governance
HighVolumeTotalThrottlesAll 14 supported types combinedSet by governance
A high-volume transaction must pass both its per-type bucket and the total bucket to be accepted. If either is exhausted, the transaction receives a BUSY response — the same behavior as the standard throttle system.
High-volume transactions use variable-rate pricing that scales with utilization. See the High-Volume Entity Creation guide to understand how this affects your transaction fees before opting in.