← previous blocknext block →recent activity

Analyzing

Block #86,958,291

25 transactions · 20 stateful · 2026-07-11 01:48:54 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,958,291  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf750850e…f822

0xd32edf…ff58

7 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x8620c47a…99dc

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x81e1b637…2b3c

0x34b655…2a6f

4 touches
1 conflict

0x88fb89dd…f591

0x34b655…2a6f

4 touches
1 conflict

0x8ca13937…b3ce

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

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

6 conflicts on slot 0xf750850eb6…b5f822

← previous block·next block →recent activity