← previous blocknext block →recent activity

Analyzing

Block #99,264,681

21 transactions · 20 stateful · 2026-08-26 07:05:06 UTC

Parallelism

62/100

Blocked

45%

Avg conflicts / tx

0.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,264,681  ·  21 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

0x748be573…77b5

0xd32edf…ff58

9 touches
10 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x91945265…e58f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x261cbea7…e35d

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

10 conflicts on slot 0x748be5730e…c677b5

← previous block·next block →recent activity