← previous blocknext block →recent activity

Analyzing

Block #99,359,093

28 transactions · 26 stateful · 2026-08-26 15:00:09 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

1.46

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,359,093  ·  28 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

0xabaad84d…1e7a

0xd32edf…ff58

13 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xfac61869…a561

0x1b6862…e19c

8 touches
6 conflicts

0x02373c43…3cb3

0x34b655…2a6f

8 touches
6 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 0xabaad84db9…741e7a

← previous block·next block →recent activity