← previous blocknext block →recent activity

Analyzing

Block #108,684,881

24 transactions · 19 stateful · 2026-09-28 06:54:24 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,684,881  ·  24 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

0xaac05511…0813

0xd32edf…ff58

9 touches
10 conflicts

0x48a29a03…c435

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xcb5d4350…46c8

0x34b655…2a6f

6 touches
3 conflicts

0xa38c430a…e3cb

0x34b655…2a6f

6 touches
3 conflicts

0x9cd1274f…0796

0x34b655…2a6f

6 touches
3 conflicts

0x90a021f0…f922

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 0xaac055115a…3c0813

← previous block·next block →recent activity