← previous blocknext block →recent activity

Analyzing

Block #86,626,407

23 transactions · 21 stateful · 2026-07-09 12:50:05 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,626,407  ·  23 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

0xb91cf328…71a4

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x472216ee…f44b

0x34b655…2a6f

4 touches
1 conflict

0x0a9a1df9…6b66

0x34b655…2a6f

4 touches
1 conflict

0x3b9a98cf…dc7c

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

10 conflicts on slot 0xb91cf32848…de71a4

← previous block·next block →recent activity