← previous blocknext block →recent activity

Analyzing

Block #108,680,023

22 transactions · 19 stateful · 2026-09-28 06:29:52 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,680,023  ·  22 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

0xd5b92a76…7fdd

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0051

0x1b6862…e19c

6 touches
3 conflicts

0x57d3b231…a40c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

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 0xd5b92a76cc…407fdd

← previous block·next block →recent activity