mev-blocks
mev-blocks copied to clipboard
Hello. The historical json dump ends at block 14986955. Any chance this can be replaced by a more current dump? Thanks!
- Increase pool size to 20. Defaults to CPU count, which is too low- there's very little processing happening and most time is spent in DB getting the data -...
Idea: expose three new timestamps in `/transactions` and `/blocks` * `block.witnessed_at` * `transaction.received_at` * `transaction.sent_to_miners_at` @jiangjinyuan already made an issue about block timetamps: https://github.com/flashbots/mev-blocks/issues/7 Returning the timestamp at which a...
* adds timestamps `received_at` and `sent_to_miners_at` to transaction response in `/transactions` and `/blocks` * adds timestamp `witnessed_at` in `/blocks` response * redundant fields `eao_address` and `eoa_address` in `/transactions/` response to...
Here is what block query should look like (with bundle_type) returned: ``` $ curl https://blocks.flashbots.net/v1/blocks?block_number=14849437 | jq '.blocks[0].transactions[0]' { "transaction_hash": "0x3c265fa66e96365cd8b0aa974d482b10e392eacb095662b230bb02bf42016239", "tx_index": 0, "bundle_type": "flashbots",
Please add the filed timestamp about the block mined in the blocks's response @jparyani
Would be awesome if i could more easily start parsing data X number of elements at the time from the oldest block with an after param. Right now i can...