← previous blocknext block →recent activity

Analyzing

Block #95,736,774

19 transactions · 18 stateful · 2026-08-13 21:20:19 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,736,774  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd353c26c…e5fa

0xd32edf…ff58

5 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x1a2a7709…4ac8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6127c8ac…3f6e

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

3 conflicts on slot 0xd353c26c55…b3e5fa

← previous block·next block →recent activity