Compute Units Table: The Art of Efficiency

This table provides a breakdown of Compute Units (CUs) associated with various Ethereum RPC requests. CUs are a measure of resource consumption, allowing users to understand and manage their usage effectively.

RPC Compute Units Table

Request	CU Cost	Additional Rules
eth_getBalance	100
eth_getTransactionCount	100
eth_sendRawTransaction	300
eth_getTransactionByHash	200
eth_call	2500
eth_getLogs	5000
eth_subscribe (new block headers)	TBD
eth_getBlockByNumber	3000
eth_getCode	200
eth_syncing	1
eth_estimateGas	1500
cgp_simulateTransactionsBundleV2	8200	Supported Chains: [Ethereum, Base L2, Linea L2, BSC, Scroll L2]
cgp_simulateTransactionsBundle	8200	Per Payload: 10, Supported Chains: [Ethereum, Base L2, Linea L2, BSC, Scroll L2], Max Payload Size: 20
cgp_simulateTransaction	8200	Per Payload: 10, Supported Chains: [Ethereum, Base L2, Linea L2, BSC, Scroll L2], Max Payload Size: 20

Note: All the other existing methods in clients are measured as 300 CU per request.

WebSockets Compute Units Cost

WebSocket API usage is priced based on bandwidth, which is the amount of data delivered as part of the subscription.

	Free Subscription	Advanced Subscription
CU Cost per 1 KB	200 CU per 1 KB	160 CU per 1 KB