← previous blocknext block →recent activity

Analyzing

Block #91,395,829

26 transactions · 24 stateful · 2026-07-29 16:50:17 UTC

Parallelism

73/100

Blocked

58%

Avg conflicts / tx

1.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,395,829  ·  26 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

0x6c704ea3…6afd

0xd32edf…ff58

13 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0672e4a2…8d1f

0x34b655…2a6f

8 touches
6 conflicts

0xf81cdf08…1f74

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0x7c09c53e…64b4

0x34b655…2a6f

6 touches
3 conflicts

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 0x6c704ea324…556afd

← previous block·next block →recent activity