← previous blocknext block →recent activity

Analyzing

Block #95,626,088

24 transactions · 20 stateful · 2026-08-13 12:02:32 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,626,088  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5fd3436f…f220

0xd32edf…ff58

7 touches
6 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x50757505…6bd7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0xb51e8dd3…98af

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

6 conflicts on slot 0x5fd3436fd2…e7f220

← previous block·next block →recent activity