← previous blocknext block →recent activity

Analyzing

Block #91,128,139

19 transactions · 17 stateful · 2026-07-28 18:22:35 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,128,139  ·  19 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

0xf704e162…76d3

0xd32edf…ff58

9 touches
10 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0x126a0344…4465

0x34b655…2a6f

4 touches
1 conflict

0x1e941f20…a68e

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x3307aebb…fe62

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 0xf704e1622b…a276d3

← previous block·next block →recent activity