← previous blocknext block →recent activity

Analyzing

Block #89,865,728

26 transactions · 22 stateful · 2026-07-24 08:10:29 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,865,728  ·  26 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

0xfac86dca…eefa

0xd32edf…ff58

5 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xcbe18c62…3a5c

0x34b655…2a6f

4 touches
1 conflict

0xcbe18c62…3a5d

0x34b655…2a6f

4 touches
1 conflict

0xd569d052…8742

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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 0xfac86dca21…14eefa

← previous block·next block →recent activity