← previous blocknext block →recent activity

Analyzing

Block #99,367,940

25 transactions · 18 stateful · 2026-08-26 15:44:46 UTC

Parallelism

84/100

Blocked

44%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,367,940  ·  25 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

0xce6c07ec…3398

0xd32edf…ff58

7 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x1674d3d4…275f

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x76c760be…7d68

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x66e5fb4e…5218

0xa6afd3…d132

3 touches
1 conflict

0xb924350c…7c11

0x754704…b603

2 touches
0 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

6 conflicts on slot 0xce6c07ec6c…d13398

← previous block·next block →recent activity