← previous blocknext block →recent activity

Analyzing

Block #98,522,631

26 transactions · 23 stateful · 2026-08-23 16:13:19 UTC

Parallelism

65/100

Blocked

61%

Avg conflicts / tx

1.73

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #98,522,631  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd9688bdc…4b99

0xd32edf…ff58

15 touches
28 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0x45de70d9…e1dc

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xd996735f…8733

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

28 conflicts on slot 0xd9688bdc69…3f4b99

← previous block·next block →recent activity