← previous blocknext block →recent activity

Analyzing

Block #89,280,585

27 transactions · 25 stateful · 2026-07-21 20:41:48 UTC

Parallelism

74/100

Blocked

68%

Avg conflicts / tx

1.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,280,585  ·  27 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

0x41f6ea02…64f9

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xee4fe1f7…3ead

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xdef75eb5…f4bf

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 0x41f6ea0258…8c64f9

← previous block·next block →recent activity