← previous blocknext block →recent activity

Analyzing

Block #95,641,913

23 transactions · 21 stateful · 2026-08-13 13:22:08 UTC

Parallelism

70/100

Blocked

52%

Avg conflicts / tx

1.3

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,641,913  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x667819be…be93

0xd32edf…ff58

13 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x06386625…6129

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0672e4a2…8d1f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0x95460253…47e7

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

21 conflicts on slot 0x667819be97…37be93

← previous block·next block →recent activity