OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Explorers & Analytics

Blockchainspider

Blockchainspider is an open-source Python and Scrapy toolkit for collecting on-chain transaction and block records, address or transaction labels, and address-centered transfer subgraphs into local CSV and JSON files.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Blockchainspider — OpenViST project profile in Explorers & Analytics.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when your work requires configurable, command-line collection of on-chain records into local datasets for later analysis, rather than a hosted visual explorer.

Who it is for

  • Developers building local blockchain data collection pipelines.
  • Researchers assembling transaction, block, label or transfer-flow datasets.
  • Analysts tracing money flows around a selected address or transaction.

Documented uses

  • Collect transactions and block metadata for a defined EVM block range.
  • Gather receipts, logs, traces and token-transfer records.
  • Build a transfer subgraph centered on an address or transaction.
  • Collect address or transaction labels into local reports.
  • Collect transaction data from Solana using a provider endpoint.
Before you choose

Requirements & limits

The repository is public, identifies an MIT license, and documents local installation. The README specifies Python 3.8–3.10; some collection examples require a provider endpoint, and the Etherscan tracing example requires an API key.

  • Collection runs through Scrapy command-line spiders and requires local setup.
  • Chain data access depends on the provider endpoint supplied to a spider.
  • The documented output formats include CSV for block, transaction and transfer records and JSON objects for label reports.
  • The README names Ethereum, BNB Chain and Polygon for EVM collection and includes a separate Solana transaction example.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Collect a bounded Ethereum block range

Use the documented EVM transaction spider to collect transaction and block records for a specified range.

Before you start

  • A local clone of the BlockchainSpider repository.
  • Python 3.8–3.10 and dependencies installed with pip install -r requirements.txt.
  • An EVM provider URL.

Steps

  1. Clone https://github.com/wuzhy1ng/BlockchainSpider.git and install its requirements.

  2. Run scrapy crawl trans.block.evm -a start_blk=19000000 -a end_blk=19000100 -a providers=https://eth.llamarpc.com.

  3. Inspect the generated files under ./data, including BlockItem.csv and TransactionItem.csv.

Expected outcome

Local CSV records for blocks and external transactions in the selected range.

Guide limitations

  • The example is for Ethereum and the specified block range; other EVM networks require an appropriate provider.
  • The README documents the command and output locations but does not establish results for other provider configurations.
Documentation 1 ↗
Source-based practical guide

Collect an address-centered Ethereum transfer subgraph

Use the documented transaction-subgraph spider to gather money-transfer data centered on a source address.

Before you start

  • A local clone of BlockchainSpider and installed dependencies.
  • An Ethereum source address.
  • An Etherscan API key and API endpoint.

Steps

  1. Clone the repository and install dependencies from requirements.txt.

  2. Run the documented scrapy crawl txs.blockscan command with the source, apikeys and endpoint arguments set for the target.

  3. Check ./data/AccountTransferItem.csv for the collected transfer data.

Expected outcome

A local CSV file containing the collected address-centered money-transfer data.

Guide limitations

  • The example uses the documented Etherscan endpoint and requires an API key.
  • The README illustrates one Ethereum source-address case; it does not establish identical behavior for other data sources.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
wuzhy1ng/BlockchainSpider · Official homepage title · retained in its source language
How we review sourcesSuggest a correction