API · /blocktime-api

Block Time API

healthy 3,939 Subscribers

Convert a timestamp or date into the block number that was live at that moment on any of 100+ blockchains, keyless. On-chain analysts, indexers and dashboards constantly need "what block was chain X at time T" to query historical state, and "which blocks cover this time window" to scan a period. This API answers both — for a single moment and for a date range (returning the start and end block plus the block count and average block time). Live, nothing stored. The timestamp-to-block layer for EVM and non-EVM chains alike. Backed by the open DeFiLlama coins API.

api.oanor.com/blocktime-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/blocktime-api/openapi.json
/api/blocktime-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
150 ms
Server probes · 24h
Subscribers
3,939
active
Total calls
15
last 7 days
status Full status page → · 9 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 6,000 calls / month
  • 3 requests / second
  • Hard cap (429 above quota, no overage)
  • 6,000 calls/month
  • 3 req/sec
  • Block-at-time + range
  • No credit card
Sign in to subscribe

Starter

€8.60 /month

  • 140,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 140k calls/month
  • 8 req/sec
  • 100+ chains
  • Email support
Sign in to subscribe

Pro

€29.50 /month

  • 900,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 900k calls/month
  • 20 req/sec
  • Indexer / backfill scale
  • Priority support
Sign in to subscribe

Business

€86.00 /month

  • 5,500,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 5.5M calls/month
  • 50 req/sec
  • Commercial use
  • Dedicated SLA
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

Masonry Estimating API

Masonry estimating maths as an API, computed locally and deterministically — the brick, block and mortar counts a bricklayer, builder or estimator works to. The brick endpoint computes how many bricks a wall needs from its area (or length × height in feet): bricks per square foot = 144 / ((brick length + joint) × (brick height + joint)), so a standard modular brick with a 3/8-inch mortar joint works out to the well-known 6.86 bricks per square foot — a 100 ft² wall is 686 bricks, plus a waste allowance and the mortar bags (about 7 per 1000 bricks). The block endpoint does the same for concrete masonry units: a standard 16×8-inch CMU with a 3/8-inch joint is 1.125 blocks per square foot, with roughly 2.5 mortar bags per 100 blocks. Both endpoints take custom unit face dimensions and joint thickness, add a configurable waste percentage and round up to whole units. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, masonry-contractor, building-supply and home-improvement app developers, takeoff and material-estimating tools, and trade calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches and square feet). Live, nothing stored. 2 compute endpoints. This is brick/block and mortar estimating; for poured-concrete volume use a concrete API and for drywall use a drywall API.

api.oanor.com/masonry-api

Snowflake ID API

Decode and build snowflake IDs — the 64-bit, time-sortable identifiers used by Twitter/X, Discord, Instagram and many distributed systems. Pass an ID and a platform and the service extracts the embedded creation timestamp (turn any Discord, Twitter/X or Instagram ID into the exact moment it was created) along with the machine and sequence components for that platform's epoch and bit layout. Supported platforms: twitter (X), discord, instagram, sony, and custom (supply your own epoch). The encode endpoint does the reverse: build the lower-bound snowflake for a given timestamp, so you can query "all IDs created at or after this moment" — the standard trick for time-based pagination on snowflake APIs. Everything is computed locally with exact 64-bit BigInt math and no network calls. Ideal for analytics, data forensics, API pagination and debugging distributed-ID systems. A snowflake-ID toolkit — distinct from UUID/ULID generation (uuid) and date/time math (datetime). No upstream key, no cache.

api.oanor.com/snowflake-api

DateTime API

A fast, fully-local date and time toolkit (UTC): parse any date string or unix timestamp into ISO, unix and components with the ISO week number, day-of-year and leap-year flag; format dates with custom tokens (YYYY-MM-DD, weekday and month names, and more); add or subtract month-aware durations; compute the difference between two dates in every unit plus a human-readable summary; and convert between unix timestamps and ISO. Every endpoint accepts input via the query string or the request body. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for scheduling, billing periods, reminders, analytics and any date arithmetic. (For the current time in a specific timezone, see the oanor Time API.)

api.oanor.com/datetime-api

Meter API

Live EVM on-chain data for Meter (chain id 82) — the HotStuff-BFT proof-of-stake Layer-1 whose native gas token is MTR — served directly from public EVM JSON-RPC nodes with multi-node failover. The status endpoint returns the chain and network id, the latest block height and the node client version. The block endpoint returns a block by number (or the latest) with its hash, parent hash, timestamp, transaction count, gas used and gas limit, miner and size. The gas endpoint returns the current gas price in both wei and gwei. The balance endpoint returns the MTR balance and outgoing transaction count for any address, converted from base wei (18 decimals) into whole MTR with exact big-integer scaling. Every figure is read live from the chain over JSON-RPC — nothing bundled or modelled — behind a short server-side cache with keep-warm so the feed stays fast and fresh. Ideal for explorers, wallet and dashboard tooling, gas trackers, address monitors and analytics apps across the Meter ecosystem. Live keyless upstream. 5 endpoints.

api.oanor.com/meter-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Block Time API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Block Time API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Block Time API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Block Time API cost?
Block Time API has a free tier with 100 calls / month. Paid plans start at €8.60 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Block Time API GDPR-compliant?
All requests to Block Time API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/blocktime-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/blocktime-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/blocktime-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/blocktime-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.