← previous blocknext block →recent activity

Analyzing

Block #99,316,639

34 transactions · 29 stateful · 2026-08-26 11:26:26 UTC

Parallelism

71/100

Blocked

59%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #99,316,639  ·  34 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x3cf48cba…9a3c

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x8d47c9a4…f11f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x920754e8…0ac6

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 0x3cf48cbacf…559a3c

← previous block·next block →recent activity