← previous blocknext block →recent activity

Analyzing

Block #89,411,966

30 transactions · 24 stateful · 2026-07-22 11:20:01 UTC

Parallelism

90/100

Blocked

25%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,411,966  ·  30 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xfc23b257…9bcc

0xd32edf…ff58

5 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x63bed776…8d4b

0x34b655…2a6f

4 touches
1 conflict

0x8ad18e06…472a

0x34b655…2a6f

4 touches
1 conflict

0xa38c430a…e3cb

0x34b655…2a6f

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd3d2b624…594f

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

3 conflicts on slot 0xfc23b257a8…229bcc

← previous block·next block →recent activity