← previous blocknext block →recent activity

Analyzing

Block #95,275,834

20 transactions · 16 stateful · 2026-08-12 06:36:08 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,275,834  ·  20 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

0xa48d8c02…840b

0xd32edf…ff58

9 touches
10 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

4 touches
1 conflict

0x1ffbc5c9…461f

0x34b655…2a6f

4 touches
1 conflict

0x309fd64b…ba48

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc13e1d5c…62c7

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xa48d8c02df…7c840b

← previous block·next block →recent activity