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:
Endpoint | Previous Compute Units | New Compute Units |
---|---|---|
/erc20/{address}/price | 3 | 10 |
/{address} | 1 | 5 |
/{address}/logs | 2 | 5 |
/{address}/erc20 | 5 | 10 |
/erc20/mints | 5 | 10 |
/erc20/burns | 5 | 10 |
/erc20/approvals | 5 | 10 |
/block/{block_number_or_hash} | 5 | 10 |
/{address}/erc20/transfers | 2 | 5 |
/erc20/{address}/transfers | 2 | 10 |
Similarly, the CUs charged for the following query parameter has changed:
Query Parameter | Previous Compute Units | New Compute Units |
---|---|---|
include=internal_transactions on /{address} | 0 | 5 |
include=internal_transactions on /transaction/{transaction_hash} | 0 | 3 |
include=internal_transactions on /block/{block_number_or_hash} | 0 | 10 |
For more information about what CUs are and how they're charged, visit our Compute Units page.