← previous blocknext block →recent activity

Analyzing

Block #103,040,939

20 transactions · 19 stateful · 2026-09-08 12:36:09 UTC

Parallelism

60/100

Blocked

58%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #103,040,939  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3f95b8bb…09e2

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x91220b8f…7a08

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x77ed432f…fa04

0x065c9d…c394

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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

15 conflicts on slot 0x3f95b8bb43…ab09e2

← previous block·next block →recent activity