RPC Keys
Compute Units

Compute Units

We use Compute Units (CUs) to measure how many computational resources (CPU, RAM, disk, etc.) an API method uses. This allows us to provide fair and transparent pricing (e.g. no over spending for simple requests).

MethodCost
debug_traceTransaction300
debug_traceCall300
debug_traceBlockByHash300
debug_traceBlockByNumber300
trace_get75
trace_block75
trace_transaction75
trace_call75
trace_rawTransaction75
trace_filter75
trace_replayTransaction3000
trace_replayBlockTransactions3000
net_version0
eth_chainId0
eth_syncing0
eth_protocolVersion0
net_listening0
eth_uninstallFilter10
eth_accounts10
eth_blockNumber10
eth_subscribe10
eth_unsubscribe10
eth_feeHistory10
eth_maxPriorityFeePerGas10
eth_createAccessList10
eth_getTransactionReceipt15
eth_getUncleByBlockHashAndIndex15
eth_getUncleByBlockNumberAndIndex15
eth_getTransactionByBlockHashAndIndex15
eth_getTransactionByBlockNumberAndIndex15
eth_getUncleCountByBlockHash15
eth_getUncleCountByBlockNumber15
web3_clientVersion15
web3_sha315
eth_getBlockByNumber15
eth_getStorageAt15
eth_getTransactionByHash15
eth_gasPrice20
eth_getBalance20
eth_getCode20
eth_getFilterChanges20
eth_newBlockFilter20
eth_newFilter20
eth_getBlockTransactionCountByHash20
eth_getBlockTransactionCountByNumber20
eth_getProof20
eth_getBlockByHash20
eth_getTransactionCount20
eth_call75
eth_getFilterLogs75
eth_getLogs75
eth_estimateGas75
eth_sendRawTransaction200
eth_getBlockReceipts200

Other methods generally priced at 20 CUs


Get started → (opens in a new tab)