Skip to main content
The free blocks subgraphs were sunset on Monday, 31 August 2026 at 12:00 UTC. A few endpoints still respond, but they are no longer maintained and will be removed without further notice. Any copy of one you deployed into your own project bills as normal subgraph usage.For block number, hash and timestamp lookups, eth_getBlockByNumber on Goldsky Edge covers the same ground. For anything else, contact support@goldsky.com and we’ll help you find the right path.
Blocks subgraphs are commonly needed for applications that require block-level data such as timestamps, block numbers, and other metadata. However, indexing blocks across an entire chain can be resource-intensive and expensive.

​
Free blocks subgraphs

Goldsky provided free, pre-indexed blocks subgraphs on the shared community project. They were always meant for exploratory use and lightweight testing with a 50/10s rate limit, never for production or scraping workloads. They are no longer maintained. Do not build on them.

​
Endpoint format

Replace {chain-slug} with the chain slug from the list below.

​
Example

To query the Base blocks subgraph:

​
Endpoints still responding

Most of these endpoints are already gone. The following still answer, unmaintained, and may stop at any time: Any network not in this list has already been removed.

​
Migrating

Goldsky Edge serves block data per request, with no subgraph to run or pay storage on. eth_getBlockByNumber returns the number, hash, parent hash and timestamp for a block, which covers most of what these subgraphs are used for. If you query blocks in a way that request-level lookups don’t cover, or you need a chain Edge doesn’t serve yet, contact support@goldsky.com and we’ll work out the right option with you.