Skip to main content

[Notice] CU change across multiple endpoints

· One min read

As outlined in an earlier post, today we have change the compute units (CUs) charged on the below endpoints will be changing as per the following table:

EndpointPrevious Compute UnitsNew Compute Units
/erc20/{address}/price310
/{address}15
/{address}/logs25
/{address}/erc20510
/erc20/mints510
/erc20/burns510
/erc20/approvals510
/block/{block_number_or_hash}510
/{address}/erc20/transfers25
/erc20/{address}/transfers210

Similarly, the CUs charged for the following query parameter has changed:

Query ParameterPrevious Compute UnitsNew Compute Units
include=internal_transactions on /{address}05
include=internal_transactions on /transaction/{transaction_hash}03
include=internal_transactions on /block/{block_number_or_hash}010

For more information about what CUs are and how they're charged, visit our Compute Units page.