← previous blocknext block →recent activity

Analyzing

Block #107,666,305

31 transactions · 23 stateful · 2026-09-24 17:26:29 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,666,305  ·  31 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

0xbee9b054…9774

0xd32edf…ff58

13 touches
21 conflicts

0x839c0c71…bada

0x34b655…2a6f

8 touches
6 conflicts

0x6a9e408e…3721

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x13bbb257…417d

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x366a19b0…f065

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

21 conflicts on slot 0xbee9b054f4…c09774

← previous block·next block →recent activity