debug_traceBlockByHash
POST/
A debugging tool that allows you to trace chain state changes caused by transactions and the history of actual calls for a specific block, by configuring a tracer and using the information it provides.
429 errors can occur when you exceed the Throughput limit of your subscription plan. For example, the Starter plan has a limit of 300 CU per second, so calling an API that consumes 350 CU while on the Starter plan may result in a 429 error. Check the CU consumption of the APIs you use on the Compute Unit Costs page, and consider upgrading to a higher plan if you need more Throughput! 👉 Go to Compute Unit Costs page
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 405
- 408
- 409
- 413
- 414
- 429
- 500
- 503
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Request Timeout
Conflict
Payload Too Large
URI Too Long
Too Many Requests
Internal Server Error
Service Unavailable