← previous blocknext block →recent activity

Analyzing

Block #108,437,042

18 transactions · 17 stateful · 2026-09-27 10:06:21 UTC

Parallelism

50/100

Blocked

65%

Avg conflicts / tx

2.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #108,437,042  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x047f6bd2…74fb

0xd32edf…ff58

17 touches
36 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0012

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…001b

0x1b6862…e19c

14 touches
21 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x8f4e041c…01ae

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

36 conflicts on slot 0x047f6bd2a7…b374fb

← previous block·next block →recent activity