← previous blocknext block →recent activity

Analyzing

Block #95,648,110

28 transactions · 24 stateful · 2026-08-13 13:53:18 UTC

Parallelism

75/100

Blocked

58%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,648,110  ·  28 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

0xec8e1069…ef5e

0xd32edf…ff58

13 touches
21 conflicts

0x9fd372a1…a959

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xa1e228bc…b93c

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x1565183a…e0a0

0x34b655…2a6f

4 touches
1 conflict

0x1bee5aea…5f61

0x34b655…2a6f

4 touches
1 conflict

0x2bd66f15…8cee

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 0xec8e1069ab…dbef5e

← previous block·next block →recent activity