Bridge Explorer: Cross-Chain Transactions by Date | Toolmu

Look up transaction records for one cross-chain bridge over a date range. Enter its name or paste its DefiLlama page link, then use everyday dates. The result is a transaction list, not a bridge-volume ranking.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use the DefiLlama bridge-list Tool list-all-bridges-along-with-summaries-of-recent-bridge-volumes-defillama to resolve the user's bridge name or DefiLlama bridge page link to one exact bridge. Never ask the user to provide a numeric ID or machine-readable time values; translate the user's calendar dates. Ask a brief plain-language follow-up if the bridge has no single exact match or the date range is unclear. When clear, call get-all-transactions-for-a-bridge-within-a-date-range-defillama. Add source-chain or wallet-address filters only if the user asks for them in everyday language. Explain that the result is transaction records for the selected bridge and period, not a bridge-volume ranking. Check current prices, balance, and authorization before any Tool calls.

Task:
Find cross-chain transactions for [bridge name or DefiLlama bridge page link] from [start date] through [end date].

Paste into your connected AI's conversation.

Connection guide

Up to 0.00072 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

DefiLlama

Bridge Explorer: Cross-Chain Transactions by Date | Toolmu

Look up transaction records for one cross-chain bridge over a date range. Enter its name or paste its DefiLlama page link, then use everyday dates. The result is a transaction list, not a bridge-volume ranking.

You receive

One call returns DefiLlama transactions for the chosen bridge and date window, up to 6,000 rows. Output fields are unpublished. Pay per call from the shared prepaid balance; one run never exceeds $0.0006. It cannot send funds or rank bridges by volume or TVL.

Start with your task

Find cross-chain transactions for [bridge name or DefiLlama bridge page link] from [start date] through [end date].

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
pathParams`pathParams`	`object`	Required	Required fields `id`
id`pathParams.id`	`integer`	Required	bridge ID, you can get these from /bridges Examples `1`
queryParams`queryParams`	`object`	Optional
limit`queryParams.limit`	`integer`	Optional	limit to number of transactions returned, maximum is 6000 Examples `200`
address`queryParams.address`	`string`	Optional	Returns only transactions with specified address as "from" or "to". Addresses are quried in the form {chain}:{address}, where chain is an identifier such as ethereum, bsc, polygon, avax... . Examples `ethereum:0x69b4B4390Bd1f0aE84E090Fe8af7AbAd2d95Cc8E`
sourcechain`queryParams.sourcechain`	`string`	Optional	Returns only transactions that are bridging from the specified source chain. Examples `Polygon`
endtimestamp`queryParams.endtimestamp`	`integer`	Optional	end timestamp (Unix timestamp) for date range Examples `1667347200`
starttimestamp`queryParams.starttimestamp`	`integer`	Optional	start timestamp (Unix Timestamp) for date range Examples `1667260800`

View raw JSON

{
  "type": "object",
  "required": [
    "pathParams"
  ],
  "properties": {
    "pathParams": {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "examples": [
            1
          ],
          "description": "bridge ID, you can get these from /bridges"
        }
      },
      "additionalProperties": true
    },
    "queryParams": {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "examples": [
            200
          ],
          "description": "limit to number of transactions returned, maximum is 6000"
        },
        "address": {
          "type": "string",
          "examples": [
            "ethereum:0x69b4B4390Bd1f0aE84E090Fe8af7AbAd2d95Cc8E"
          ],
          "description": "Returns only transactions with specified address as \"from\" or \"to\". Addresses are quried in the form {chain}:{address}, where chain is an identifier such as ethereum, bsc, polygon, avax... ."
        },
        "sourcechain": {
          "type": "string",
          "examples": [
            "Polygon"
          ],
          "description": "Returns only transactions that are bridging from the specified source chain."
        },
        "endtimestamp": {
          "type": "integer",
          "examples": [
            1667347200
          ],
          "description": "end timestamp (Unix timestamp) for date range"
        },
        "starttimestamp": {
          "type": "integer",
          "examples": [
            1667260800
          ],
          "description": "start timestamp (Unix Timestamp) for date range"
        }
      },
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.