Collect by transaction hash

The following arguments for trans.evm can be set, including:

• out: the output directory; the default is ./data.

• hash: specific transaction hashes for collecting transaction data, if there are multiple, please join them with ,.

• providers: the HTTP JSON RPC providers. If you have two or more providers, you can use , to join them.

• enable: Specify the transaction crawler middleware to be started. If multiple middlewares are enabled, please separate them with ,. Middlewares determine which data will be collected. BlockchainSpider provides the following middlewares:

  • BlockchainSpider.middlewares.trans.TransactionReceiptMiddleware

  • BlockchainSpider.middlewares.trans.TraceMiddleware

  • BlockchainSpider.middlewares.trans.TokenTransferMiddleware

  • BlockchainSpider.middlewares.trans.TokenPropertyMiddleware

  • BlockchainSpider.middlewares.trans.ContractMiddleware

  • BlockchainSpider.middlewares.trans.DCFGMiddleware

Use case: collect trace, receipt and token transfers of transactions

scrapy crawl trans.evm \
-a out=/path/to/output/data \
-a hash=0x863bcf753e2805010e3db87a32c3d60c5a85dffce80b5da6c6236ab9f7c4d592,0xb8020a861ad97188ddf794fd61b4eb17eea1b9e6e21296e01dcab28b50016a06\
-a providers=https://freerpc.merkle.io \
-a enable=BlockchainSpider.middlewares.trans.TransactionReceiptMiddleware,BlockchainSpider.middlewares.trans.TraceMiddleware,BlockchainSpider.middlewares.trans.TokenTransferMiddleware,BlockchainSpider.middlewares.trans.TokenPropertyMiddleware