Address Dimension Query: Transaction History and On-Chain Data Retrieval

Understanding Address-Based Queries

Address dimension queries allow you to retrieve transaction histories associated with specific blockchain addresses, sorted in reverse chronological order. This functionality is essential for:

Tracking fund movements
Auditing wallet activity
Analyzing on-chain behavior patterns
Monitoring transaction statuses

API Request Structure

Endpoint

GET `https://web3.okx.com/api/v5/wallet/post-transaction/transactions-by-address`

Required Parameters

Parameter	Type	Description
`address`	String	Target blockchain address
`chains`	String	Comma-separated chain identifiers (max 50)

Optional Parameters

Parameter	Type	Description
`tokenAddress`	String	Filter by token contract address
`begin`/`end`	String	Timestamp range (milliseconds)
`cursor`	String	Pagination marker
`limit`	String	Results per query (default: 20)

👉 Discover advanced blockchain query techniques

Response Data Structure

The API returns comprehensive transaction details including:

Chain identification: chainIndex
Transaction metadata: txHash, nonce, txTime
Financial data: amount, symbol, txFee
Status indicators: txStatus, hitBlacklist
Participant details: from/to arrays with addresses and amounts

| Field            | Type    | Description |
|------------------|---------|-------------|
| `transactionList`| Array   | Complete transaction records |
| `cursor`         | String  | Pagination reference |

Practical Implementation

Key Features

Supports multi-chain queries (up to 50 chains simultaneously)
Flexible time window filtering
Detailed token-specific filtering
Comprehensive transaction status reporting

👉 Explore real-world API implementation examples

FAQ Section

How do I handle pagination in large transaction sets?

Use the cursor parameter from the response to sequentially request additional batches of transactions.

What's the difference between iType values?

0: Native currency transfers
1: Internal contract transfers
2: Token transfers

How current is the transaction data?

All data reflects real-time blockchain state with typical propagation delays of 1-2 blocks.

Can I filter by transaction status?

While the API doesn't support direct status filtering, you can process the txStatus field locally.

What's the maximum historical depth available?

The API provides complete transaction history for any address since its creation.

How are multi-chain queries handled?

Specify multiple chains in the chains parameter to get consolidated results across networks.

Best Practices

For monitoring applications, implement regular polling with time-based filtering
Cache frequent queries to reduce API calls
Always verify txStatus before considering transactions final
Use blacklist indicators (hitBlacklist) for security screening

This comprehensive guide provides everything developers need to implement robust address-based query functionality. For more specialized requirements, consult the full API documentation.