← previous blocknext block →recent activity

Analyzing

Block #106,954,126

32 transactions · 29 stateful · 2026-09-22 05:40:11 UTC

Parallelism

69/100

Blocked

48%

Avg conflicts / tx

1.75

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,954,126  ·  32 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

0xd184c355…b309

0xd32edf…ff58

13 touches
21 conflicts

0xfcd5e68f…2a12

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xa140ac77…1f0c

0x34b655…2a6f

10 touches
10 conflicts

0x4f089e20…f71a

0x34b655…2a6f

8 touches
6 conflicts

0x51aa664e…d3b8

0x34b655…2a6f

8 touches
6 conflicts

0x5969523e…5191

0x34b655…2a6f

8 touches
6 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

8 touches
6 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 0xd184c3554d…0eb309

← previous block·next block →recent activity