Block by date
Choose a UTC cutoff and your own HTTPS RPC endpoint for Ethereum or BNB Smart Chain.
Result
Enter the inputs above.
How the lookup works
The browser confirms the endpoint’s chain ID, freezes the latest block and searches block timestamps for the greatest height at or before your UTC instant. It verifies the selected block and its successor. At most 80 read requests are allowed, each with a timeout. Errors stop the lookup; no automatic retry occurs.
What the result establishes
The result establishes a timestamp bracket in the observed chain view. It does not establish consensus finality or historical state availability. A date at or after the frozen head and a date before chain history are rejected. Recent blocks can change, and a header lookup does not prove a later historical token call will succeed.
Your endpoint and privacy
Requests go directly from your browser to the HTTPS URL you enter, with credentials omitted and no referrer. The RPC operator receives the requests and your connection information. This website does not receive or store the endpoint, any key embedded in its URL, or the result. Avoid using a secret-bearing endpoint on a shared computer. CORS support is required and cannot be bypassed by this static tool.
For a detailed explanation, read the block-by-date draft and Historical Balance API concepts.
Is this an Indexbase API query?
No. It is a client-side calculation using only the RPC endpoint you supply.
Does the tool prove finality?
No. It verifies a timestamp bracket and reports the observed block identity.
Why can a valid endpoint fail?
Browser CORS policy, method support, unavailable blocks, quotas or a changed chain view can prevent a result. The tool stops without silently changing the query.
Build with better context.
Get an update when private beta opens.