← previous blocknext block →recent activity

Analyzing

Block #91,077,283

21 transactions · 21 stateful · 2026-07-28 14:06:41 UTC

Parallelism

67/100

Blocked

62%

Avg conflicts / tx

1.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,077,283  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0ba31338…8e0d

0xd32edf…ff58

13 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x15ae3bf3…2507

0x34b655…2a6f

6 touches
3 conflicts

0x0835f2d8…e06a

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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

21 conflicts on slot 0x0ba31338bb…558e0d

← previous block·next block →recent activity