← previous blocknext block →recent activity

Analyzing

Block #86,448,704

28 transactions · 25 stateful · 2026-07-08 17:00:46 UTC

Parallelism

64/100

Blocked

68%

Avg conflicts / tx

2.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,448,704  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xe1b4defd…2b48

0xd32edf…ff58

19 touches
45 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a751d7a…247c

0xa6afd3…d132

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: FastLane: FastLaneAuctionHandler

45 conflicts on slot 0xe1b4defdd2…5d2b48

← previous block·next block →recent activity