← previous blocknext block →recent activity
Analyzing
Block #89,403,396
21 transactions · 20 stateful · 2026-07-22 10:22:43 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,403,396 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w29w311w012w113w214w316w417w518w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fbd5ec9…7fb4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0xb5f244d5…f550
0x34b655…2a6f
6 touches
3 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: Perpl
10 conflicts on slot 0x6fbd5ec97b…267fb4
Audit this contract →
← previous block·next block →recent activity