Hive Application Framework
Block Explorer
Blockchain API for Hive
Query transactions, accounts, witnesses and blocks through a clean REST API. No node required.
API Reference
16 endpoints across 5 groups.
Witnesses
5 endpoints- GET
/witnessesRetrieve all witnesses with pagination and sorting
- GET
/witnesses/{account-name}Detailed info for a specific witness
- GET
/witnesses/{account-name}/votersAccounts voting for a witness
- GET
/witnesses/{account-name}/voters/countVoter count for a witness
- GET
/witnesses/{account-name}/votes/historyVote history for a witness
Accounts
5 endpoints- GET
/accounts/{account-name}Account balances and parameters
- GET
/accounts/{account-name}/authorityCryptographic key authorities
- GET
/accounts/{account-name}/proxy-powerDelegators and vested power
- GET
/accounts/{account-name}/comment-permlinksPost/comment identifiers
- GET
/accounts/{account-name}/operations/comments/{permlink}Operations for a post/comment
Block Search
1 endpoint- GET
/block-searchFind blocks by operation type, account, time range
Transactions
1 endpoint- GET
/transaction-statisticsAggregated transaction counts by day/month/year
Utility
4 endpoints- GET
/versionApplication version
- GET
/last-synced-blockMost recent synced block number
- GET
/input-type/{input-value}Determine if input is block, hash, or account
- GET
/operation-type-countsHistogram of operation types
See it in action
No authentication required. Just HTTP GET.
- Track account balances across token types
- Browse block operations in real-time
- Monitor witness rankings and votes
- Search transaction history by operation type
curl "https://api.hive.blog/hafbe-api/accounts/blocktrades"
"id": 440,
"name": "blocktrades",
"can_vote": true,
"reputation": 69,
"balance": 29594875,
"vesting_shares": "8172549681941451",
"witnesses_voted_for": 9,
"is_witness": true
curl "https://api.hive.blog/hafbe-api/witnesses?limit=3&sort=votes&direction=desc" [
"witness": "blocktrades",
"rank": 1,
"votes": "128736512847",
"voters_num": 1043,
"is_active": true
,
"witness": "gtg",
"rank": 2,
"votes": "125891034562",
"voters_num": 987,
"is_active": true
,
"witness": "good-karma",
"rank": 3,
"votes": "119234567890",
"voters_num": 876,
"is_active": true
] curl "https://api.hive.blog/hafbe-api/last-synced-block"
"last_synced_block": 95123456
16 endpoints available — See full API docs
What's Inside
Three components, each with its own schema and sync process.
[balance-tracker]
syncs = ["HIVE", "HBD", "VESTS"]
tracks = ["savings", "delegations"]
history = true
[reputation-tracker]
syncs = ["reputation", "authority"]
monitor = ["key-changes"]
[hafah]
type = "Account History API"
replay = false
format = ["JSON-RPC", "REST"]
filter = "operations" - SQL-first architecture
- Smart Caching < 100ms
- Fork Resistant
- OpenAPI 3.1
How it works
- 1
Hive Network
3-second block time, DPoS consensus, 20 witnesses
- 2
HAF Sync
10k blocks/batch, automatic fork detection + rollback
- 3
PostgreSQL
Custom indexes, full SQL power
- 4
PostgREST
PL/pgSQL → REST endpoint, zero config
- 5
Your App
No SDK, no auth, HTTP GET → JSON