SQL Explorer gives you direct SQL access to billions of rows of indexed blockchain data, without managing infrastructure. Query trades, orders, positions, liquidations, and more using standard SQL, all within the same platform you already use for RPC and Streams.
SQL Explorer is currently in Beta. We are actively expanding dataset coverage and adding new features based on user feedback.
Install the Quicknode Skill to equip your agent with full knowledge of SQL Explorer and the broader Quicknode platform:
npx skills add quiknode-labs/blockchain-skills
For SQL query generation, download the machine-readable schema and include in your agent's context. See the Schema Reference for full details.
SQL Explorer enables flexible querying of indexed blockchain data using standard SQL. Instead of relying on predefined API endpoints, you can write custom queries directly against the underlying datasets.
Key characteristics:
SQL Explorer includes tools for querying, analyzing, and integrating blockchain data:
GROUP BY, and JOINhttps://api.quicknode.com/sql/rest/v1/query with API key authenticationSQL Explorer is available through the Quicknode Dashboard for interactive queries and the REST API for programmatic access.
The Quicknode Dashboard provides an interactive environment for building, testing, and visualizing SQL queries:
The REST API allows you to execute SQL queries programmatically.
SQL queries are executed via HTTP POST request to https://api.quicknode.com/sql/rest/v1/query using your Quicknode API key. Results are returned as JSON with query execution statistics.
Get the API Call from Dashboard:
After running a query in the SQL Explorer Dashboard, click API in the top to generate a ready-to-use cURL request with your query included.
Example Request:
curl -X POST 'https://api.quicknode.com/sql/rest/v1/query' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-H 'x-api-key: YOUR_API_KEY' \
-d '{
"query": "SELECT time, validator, reward, block_number FROM hyperliquid_validator_rewards ORDER BY block_number DESC LIMIT 100",
"clusterId": "hyperliquid-core-mainnet"
}'
Example Response:
{
"meta": [
{
"name": "time",
"type": "DateTime64(6, 'UTC')"
}
],
"data": [
{
"time": "2026-03-30 16:24:00.058516",
"validator": "0xf8efb4cb844a8458114994203d7b0bfe2422a288",
"reward": 0.18548686,
"block_number": 940269912
},
{
"time": "2026-03-30 16:24:00.058516",
"validator": "0xeeee86f718f9da3e7250624a460f6ea710e9c006",
"reward": 0.50774076,
"block_number": 940269912
}
],
"rows": 100,
"rows_before_limit_at_least": 120,
"statistics": {
"elapsed": 0.073805665,
"rows_read": 71918,
"bytes_read": 5322148
}
}
Understanding the Response:
The API response contains the following fields:
meta: Array of column metadata with name and type for each column in the result setdata: Array of objects containing the actual query results, with each object representing one rowrows: Number of rows returned in this responserows_before_limit_at_least: Total number of rows that matched the query before applying LIMIT (useful for pagination)statistics: Performance metrics for query optimization:
elapsed: Total query execution time in secondsrows_read: Total number of rows scanned during execution (may be more than returned rows due to filtering)bytes_read: Total data scanned in bytes (helpful for understanding query cost and optimization opportunities)Use the statistics fields to understand query performance and optimize scans. Lower rows_read and bytes_read generally indicate more efficient queries.
See the REST API Overview guide for detailed instructions, authentication setup, and examples.
Query results are limited to 1000 rows per request. For larger result sets, use LIMIT and OFFSET clauses to paginate through results. See the Pagination guide for complete examples and best practices.
Explore the SQL Explorer Cookbook for 40+ pre-built queries covering wallet activity, validator rewards, liquidations, and more. Each example includes customizable parameters and ready-to-use code in SQL, cURL, TypeScript, and Python.
SQL Explorer uses API credits from your existing Quicknode account. Credit usage is calculated server-side based on the resources consumed by each query:
Each API response includes the credit cost in the X-Credits response header, along with execution statistics (elapsed, rows_read, bytes_read) in the response body so you can monitor and optimize query costs.
Tips to reduce credit usage:
user when possible - this leverages pre-sorted projections for fast lookupsLIMIT to cap result sizeEXPLAIN to preview the query plan before executing expensive queriesYou can view your credit usage in the Quicknode Dashboard.
SQL Explorer currently supports the following chains with additional chains coming soon:
SQL Explorer provides comprehensive coverage of Hyperliquid HyperCore with billions of rows of indexed data across multiple tables including trades, orders, fills, funding, market data, and more.
Browse the complete schema reference for column definitions, data types, sort keys, and partitioning details. The schema is continuously updated and optimized for querying.
If you have any feedback or questions about this documentation, let us know. We'd love to hear from you!