πŸ”© Compute Units (CUs)

Explanation for what Compute Units are and how we use them.

With our new compute unit model, each method is assigned a CU number, derived from global average durations of each method. This allows pricing to be immune to latency changes and additionally allows for β€œweighted” rate limits.

Raw Method Costs

Method

CU

eth_uninstallFilter

10

eth_accounts

10

eth_blockNumber

10

eth_chainId

10

eth_protocolVersion

10

eth_syncing

10

net_listening

10

net_version

10

eth_subscribe

10

eth_unsubscribe

10

eth_getTransactionReceipt

15

eth_getUncleByBlockHashAndIndex

15

eth_getUncleByBlockNumberAndIndex

15

eth_getTransactionByBlockHashAndIndex

15

eth_getTransactionByBlockNumberAndIndex

15

eth_getUncleCountByBlockHash

15

eth_getUncleCountByBlockNumber

15

web3_clientVersion

15

web3_sha3

15

alchemy_getTokenMetadata

16

eth_getBlockByNumber

16

eth_getStorageAt

17

eth_getTransactionsByHash

17

trace_get

17

alchemy_getTokenAllowance

19

eth_gasPrice

19

eth_getBalance

19

eth_getCode

19

eth_getProof

21

eth_getBlockByHash

21

trace_block

24

eth_getTransactionCount

26

eth_call

26

alchemy_getTokenBalances

26

trace_transaction

26

eth_getFilterLogs

75

eth_getLogs

75

trace_call

75

trace_callMany

75

trace_rawTransaction

75

trace_filter

75

eth_estimateGas

87

eth_sendRawTransaction

250

debug_traceTransaction

309

trace_replayTransaction

2983

trace_replayBlockTransactions

2983

WebSocket and Webhook Costs

Webhook and WebSocket subscriptions on Alchemy are priced based on bandwidth: the amount of data delivered as part of the subscription.

Each subscription type is priced identically, per byte:

Bandwidth

CU

1 byte

.04

On average, a typical webhook or WebSocket subscription event is about 1000 bytes, so would consume 40 compute units. Note that this can vary significantly based on the specific event delivered.