← previous blocknext block →recent activity

Analyzing

Block #94,476,624

25 transactions · 16 stateful · 2026-08-09 11:25:02 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,476,624  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa40f5734…2255

0xd32edf…ff58

9 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x846d8f18…5c8c

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6426

0x34b655…2a6f

6 touches
3 conflicts

0x5e71af98…bfd6

0x34b655…2a6f

4 touches
1 conflict

0x70a7b5d6…fe0e

0x34b655…2a6f

4 touches
1 conflict

0x6254804c…a03c

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

10 conflicts on slot 0xa40f57341d…172255

← previous block·next block →recent activity