← previous blocknext block →recent activity
Analyzing
Block #89,563,071
20 transactions · 18 stateful · 2026-07-23 04:09:28 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,563,071 · 20 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
4w05w17w210w111w214w317w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f394483…ff62
0x34b655…2a6f
8 touches
6 conflicts
0x1e2e43de…2092
0x34b655…2a6f
8 touches
6 conflicts
0x9db3090e…7fb8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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: Perpl
6 conflicts on slot 0x4f39448303…4fff62
Audit this contract →
← previous block·next block →recent activity