← previous blocknext block →recent activity

Analyzing

Block #92,807,040

19 transactions · 13 stateful · 2026-08-03 15:11:08 UTC

Parallelism

84/100

Blocked

46%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #92,807,040  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x83420f72…a813

0xd32edf…ff58

5 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x53ca1284…cb2c

0x34b655…2a6f

4 touches
1 conflict

0xa8ea9a1c…ab1f

0x34b655…2a6f

4 touches
1 conflict

0xba9f9225…2ead

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd59b7c91…d1ef

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

3 conflicts on slot 0x83420f72d9…3ea813

← previous block·next block →recent activity