Skip to main content
The free blocks subgraphs have been sunset and removed. The endpoints below no longer return data. 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.

​
Endpoint format

Replace {chain-slug} with the slug of the chain, for example base.

​
Example

To query the Base blocks subgraph:

​
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. We have a better replacement in beta. If you’re interested, email support@goldsky.com.