Response Structure
The API returns a JSON object with the following top-level fields:Field | Description | Type |
---|---|---|
next_offset | Pagination token for the next page of results | string/null |
transactions | Array of transaction objects | array |
Transaction Object Fields
Each item in thetransactions
array contains the following fields:
Field | Description | Type |
---|---|---|
address | Wallet address | string |
block_slot | Block’s sequential index | number |
block_time | Timestamp of block creation (in microseconds) | number |
chain | Name of the blockchain | string |
raw_transaction | Raw transaction data from the RPC node at the time of ingestion | object |
See getTransaction RPC Method for more details about
raw_transaction
.Ordering
The data is ordered by descending block time, so that new transactions will always be delivered first.Pagination
This endpoint is using cursor based pagination. You can use thelimit
parameter to define the maximum page size.
Results might at times be less than the maximum page size.
The next_offset
value is included in the response and can be utilized to fetch the next page of results by passing it as the offset
query parameter in the next request.
You can only use the value from
next_offset
to set the offset
parameter of the next page of results. Using your own offset
value will not have any effect.Compute Unit Cost
The SVM Transactions endpoint has a fixed CU cost of 1 per request. See the Compute Units page for detailed information.Headers
API key to access the service
Path Parameters
SVM wallet address
Query Parameters
Maximum number of results to return. Default is 100 when not provided. Values above 1000 are reduced to 1000.
Required range:
1 <= x <= 1000
Pagination offset from previous response