← previous blocknext block →recent activity

Analyzing

Block #107,807,046

24 transactions · 22 stateful · 2026-09-25 05:15:41 UTC

Parallelism

71/100

Blocked

64%

Avg conflicts / tx

1.54

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,807,046  ·  24 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

0x6e70629a…eb44

0xd32edf…ff58

13 touches
21 conflicts

0x93afca4c…b47f

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x95523e2a…4c01

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

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 0x6e70629a84…e1eb44

← previous block·next block →recent activity