← previous blocknext block →recent activity

Analyzing

Block #106,554,098

22 transactions · 20 stateful · 2026-09-20 20:05:46 UTC

Parallelism

55/100

Blocked

55%

Avg conflicts / tx

2.91

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,554,098  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb1a4ea94…dd7d

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…001d

0x1b6862…e19c

18 touches
36 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

18 touches
36 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…0012

0x1b6862…e19c

18 touches
36 conflicts

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

14 touches
21 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

14 touches
21 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

45 conflicts on slot 0xb1a4ea9406…f3dd7d

← previous block·next block →recent activity