← previous blocknext block →recent activity

Analyzing

Block #108,576,733

36 transactions · 25 stateful · 2026-09-27 21:49:44 UTC

Parallelism

81/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,576,733  ·  36 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

0x457c1d32…cc47

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0xc8525006…2b45

0x34ae4d…3fc5

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

6 touches
3 conflicts

0x06e40499…165e

0x34ae4d…3fc5

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

21 conflicts on slot 0x457c1d32cd…f4cc47

← previous block·next block →recent activity