← previous blocknext block →recent activity

Analyzing

Block #89,668,411

24 transactions · 21 stateful · 2026-07-23 15:34:19 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,668,411  ·  24 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

0x5c0433f6…29df

0xd32edf…ff58

13 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x80656e3b…9240

0x34b655…2a6f

6 touches
3 conflicts

0x07b5c6c6…8867

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

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 0x5c0433f65c…7e29df

← previous block·next block →recent activity