← previous blocknext block →recent activity
Analyzing
Block #89,528,288
20 transactions · 19 stateful · 2026-07-23 00:17:10 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,528,288 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w07w18w19w211w312w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
6 touches
3 conflicts
0xadccdabf…b8a6
0x34b655…2a6f
6 touches
3 conflicts
0x252771a6…3918
0x34b655…2a6f
4 touches
1 conflict
0x36efab8d…c43f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7b41d5cd…00e6
0x34b655…2a6f
4 touches
1 conflict
0xa77cc9c9…2d1f
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
3 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity