← previous blocknext block →recent activity

Analyzing

Block #95,008,204

19 transactions · 17 stateful · 2026-08-11 08:00:15 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,008,204  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc8d8d282…e95b

0xd32edf…ff58

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x11b69a7e…334e

0x01bff4…1071

4 touches
1 conflict

0x0778475b…bd75

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0xc8d8d282fe…b8e95b

← previous block·next block →recent activity