← previous blocknext block →recent activity

Analyzing

Block #108,497,001

25 transactions · 24 stateful · 2026-09-27 15:08:12 UTC

Parallelism

56/100

Blocked

58%

Avg conflicts / tx

2.04

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #108,497,001  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x086b3c8f…f29a

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…001c

0x1b6862…e19c

12 touches
15 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

8 touches
6 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

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

36 conflicts on slot 0x086b3c8f72…31f29a

← previous block·next block →recent activity