← previous blocknext block →recent activity

Analyzing

Block #99,252,120

16 transactions · 15 stateful · 2026-08-26 06:01:48 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,252,120  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1559b5cc…2eb7

0xd32edf…ff58

7 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xcbd03a30…ed12

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf195ad96…e0c3

0x34b655…2a6f

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

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

6 conflicts on slot 0x1559b5cc60…072eb7

← previous block·next block →recent activity