Skip to main content

Overview

Two complementary datasets covering arbitrage cycle topology and lifecycle.
  • Dataset IDs: 0801 (paths), 0802 (path status)
  • Tables: blockdb_evm.b0801_arb_paths_v1, blockdb_evm.b0801_arb_path_status_v1
  • Description: Undirected arbitrage cycle topology (paths) and their per-event active/inactive status transitions (path status).
  • Primary keys: path_id (paths); (path_id, block_number, tx_index, log_index) (path status)
  • API: POST /evm/arb/paths, POST /evm/arb/path-status
  • CSV Sample (paths): Download
  • JSON Sample (paths): Download

Sample Viewer

Arbitrage paths (blockdb_evm.b0801_arb_paths_v1)

The paths table is the topology registry for arbitrage cycles. One row is written the first time a given cycle is detected on-chain. A cycle is an undirected loop of pools and tokens — for example a two-hop A → B → A or a three-hop A → B → C → A — where swapping around the loop could yield a net profit. The path_id is a stable 32-byte hash of the cycle topology and serves as the join key for the path status and opportunities tables. Primary key: path_id

Arbitrage path status (blockdb_evm.b0801_arb_path_status_v1)

The path status table records every activation and deactivation event for each path. A path becomes active when all its constituent pools are live and arbitrageable; it becomes inactive when a pool in the cycle is deactivated, has insufficient liquidity, or its reserves change in a way that closes the opportunity. Each row captures the exact on-chain event that caused the transition, making it possible to reconstruct the full activation history of any path. Primary key: (path_id, block_number, tx_index, log_index)

Arbitrage opportunities

Profit estimates per path and on-chain position.

Liquidity Pools

Pool metadata for the pools referenced in each cycle.
Last modified on April 4, 2026