List ERC-20 transfers
Description
Section titled “Description”Returns ERC-20 Transfer events emitted on the Bittensor EVM chain. Each row captures the transaction hash, from and to addresses, transferred amount, the token contract (address, name, symbol, decimals) and the block number and timestamp the transfer was included in.
Use address to match either side of a transfer, or from/to to fix a direction; combine with token_address, token_symbol, block_start/block_end, timestamp_start/timestamp_end, or amount_min/amount_max to narrow the result set. Pair with /api/evm/erc20/account/v1 for current balances and /api/evm/erc20/token/v1 for contract metadata.
Endpoint
Section titled “Endpoint”GET /api/evm/erc20/transfer/v1Parameters
Section titled “Parameters”| Name | In | Type | Required | Description |
|---|---|---|---|---|
block_number | query | integer | ||
block_start | query | integer | Start of block range (inclusive) | |
block_end | query | integer | End of block range (inclusive) | |
timestamp_start | query | integer | Start of timestamp range in Unix timestamp (seconds since 1970-01-01) (inclusive) | |
timestamp_end | query | integer | End of timestamp range in Unix timestamp (seconds since 1970-01-01) (inclusive) | |
address | query | string | ||
to | query | string | ||
from | query | string | ||
transaction_hash | query | string | ||
token_name | query | string | ||
token_symbol | query | string | ||
token_address | query | string | ||
amount_min | query | string | Minimum amount (inclusive) | |
amount_max | query | string | Maximum amount (inclusive) | |
page | query | integer | ||
limit | query | integer | ||
order | query | — |
Responses
Section titled “Responses”200 — Transfers retrieved successfully
Section titled “200 — Transfers retrieved successfully”Media: application/json
Schema
{ "type": "object", "required": [ "pagination", "data" ], "properties": { "data": { "type": "array", "items": { "type": "object", "required": [ "block_number", "timestamp", "transaction_hash", "to", "from", "amount", "token_decimals", "token_name", "token_symbol", "token_address" ], "properties": { "amount": { "type": "string" }, "block_number": { "type": "integer", "format": "int32" }, "from": { "type": "string" }, "timestamp": { "type": "string", "format": "date-time" }, "to": { "type": "string" }, "token_address": { "type": "string" }, "token_decimals": { "type": "integer", "format": "int32" }, "token_name": { "type": "string" }, "token_symbol": { "type": "string" }, "transaction_hash": { "type": "string" } } } }, "pagination": { "type": "object", "required": [ "current_page", "per_page", "total_items", "total_pages" ], "properties": { "current_page": { "type": "integer", "format": "int32" }, "next_page": { "type": "integer", "format": "int32", "nullable": true }, "per_page": { "type": "integer", "format": "int32" }, "prev_page": { "type": "integer", "format": "int32", "nullable": true }, "total_items": { "type": "integer", "format": "int32" }, "total_pages": { "type": "integer", "format": "int32" } } } }}400 — Bad request
Section titled “400 — Bad request”404 — Transfers not found
Section titled “404 — Transfers not found”500 — Internal server error
Section titled “500 — Internal server error”Try it
Section titled “Try it”Interactive request console coming soon. In the meantime you can use the OpenAPI spec with any client (Insomnia, Bruno, Scalar, curl).
Authentication
Section titled “Authentication”All Taostats API requests require an Authorization header containing your API key. See Getting Started.