Skip to main content

Showing wallet history with Blockscout REST API

This example uses REST methods with the PRO API. See the PRO API overview for information on creating and using an API key.
Creating a simple portfolio tracker or wallet UI requires fetching and displaying address, account, and transaction information. At a minimum you may want to display:
  • Native token and ERC20/NFT balances
  • All Transaction activity and status
  • Human-readable method summaries
In this brief guide we show the methods you would prioritize for display, pagination formatting, and a Typescript example that fetches wallet transactions and a summary of each transaction, then prints a human-readable activity list.

Endpoint Summary

The following REST calls can be used to get data for a wallet app:

1. Load wallet overview

Use this for:
  • native balance
  • ENS / tags / address metadata
  • wallet header

2. Load wallet transactions

Use this for:
  • wallet activity list
  • transaction status
  • value, timestamp, method, counterparty

3. Load token transfers

Use this for:
  • ERC-20 transfers
  • NFT transfers
  • token activity tabs or merged activity feeds

4. Load human-readable summaries

Use this when you want to show something better than raw method names. Instead of displaying:
  • transfer
  • multicall
  • execute
you can display:
  • “Sent 12.5 USDC”
  • “Swapped ETH for USDT”
  • “Approved USDC spending”
That is the fastest way to make wallet history human-readable.

Pagination

REST responses use keyset pagination. When a response includes next_page_params, copy that object and append its fields to the next request. Example:
Next request:
Then repeat the same pattern with the new next_page_params from that response.

TypeScript example

This example:
  • fetches wallet transactions
  • fetches a summary for each transaction
  • prints a human-readable activity list