← previous blocknext block →recent activity

Analyzing

Block #91,111,392

27 transactions · 19 stateful · 2026-07-28 16:58:21 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,111,392  ·  27 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

0x1defa704…d510

0xd32edf…ff58

9 touches
10 conflicts

0x217bd767…b79e

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x599dbed7…e39c

0x34b655…2a6f

4 touches
1 conflict

0x2db7dcf7…32e5

0x34b655…2a6f

4 touches
1 conflict

0x84d74093…7808

0x34b655…2a6f

4 touches
1 conflict

0xb42b9aa1…558a

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 0x1defa704ec…b4d510

← previous block·next block →recent activity