← previous blocknext block →recent activity

Analyzing

Block #88,343,212

28 transactions · 18 stateful · 2026-07-17 12:12:04 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,343,212  ·  28 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

0x5d68cf99…a69a

0xd32edf…ff58

7 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x60e95cf4…3f88

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0xa8c2feff…ecc3

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

6 conflicts on slot 0x5d68cf9977…72a69a

← previous block·next block →recent activity