← previous blocknext block →recent activity

Analyzing

Block #99,182,226

30 transactions · 20 stateful · 2026-08-26 00:10:08 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,182,226  ·  30 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

0xb5c4d5d4…7b80

0xd32edf…ff58

13 touches
21 conflicts

0x889d5e90…929a

0x2a68ba…90c5

10 touches
10 conflicts

0x348fda08…7e96

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xedee7e09…6888

0x34b655…2a6f

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

21 conflicts on slot 0xb5c4d5d4bd…a77b80

← previous block·next block →recent activity