Skip to main content

​
DeFi Dashboards and Analytics

DeFi products usually need a mix of wallet state, market data, and event monitoring. Uniblock helps by combining normalized token and transaction data with market-data endpoints and optional provider-specific access through Direct API.

​
Best-fit use cases

  • Token watchlists and market overview pages
  • Treasury dashboards for protocol-owned assets
  • Yield, LP, or vault monitoring tools
  • Internal analytics for on-chain protocol activity
Key endpoints to start with:
  • GET /market-data/price
  • GET /market-data/history
  • GET /market-data/chart-range
  • GET /market-data/trending
  • GET /token/balance
  • GET /token/transfers
  • GET /transactions

​
Suggested implementation flow

​
1. Build the market layer

Use market-data endpoints to power:
  • spot prices
  • 24 hour volume
  • historical charts
  • trending or top-moving token lists
curl --location \
  'https://api.uniblock.dev/uni/v1/market-data/price?chainId=1&tokenAddress=0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' \
  --header 'x-api-key: YOUR_API_KEY'

​
2. Add protocol and treasury positions

Use token balance and transaction endpoints to monitor wallets tied to:
  • protocol treasuries
  • reward distribution wallets
  • multisigs
  • liquidity management accounts

​
3. Add event-driven workflows

If a dashboard needs to react quickly to transfers or contract activity, add: These are useful for vault deposits, treasury movements, and settlement events.

​
4. Use Direct API when you need provider-specific depth

Some DeFi products eventually need provider-native features or niche datasets. That is where Direct API is the right extension point.
Start with Unified API for portability. Move into Direct API only when the unified schema does not expose the specific provider feature you need.

​
Where JSON-RPC fits

Use JSON-RPC for:
  • contract reads with eth_call
  • pending state inspection
  • gas estimation
  • raw transaction submission from backend services
This is useful when your DeFi backend must interact with contracts directly rather than just read indexed data.

​
Common pitfalls

DeFi apps often mix indexed data and node data. Be explicit about which layer is used for pricing, balances, and execution-critical reads.
If a view is latency-sensitive, avoid over-fetching multiple chart and balance endpoints in the same render path. Split summary views from detailed panels.