← previous blocknext block →recent activity
Analyzing
Block #89,682,610
16 transactions · 16 stateful · 2026-07-23 16:46:33 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,682,610 · 16 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
1w02w13w04w05w17w28w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x6b2cd1a2…4685
0x34b655…2a6f
4 touches
1 conflict
0x6dc9ce62…9b3b
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x7118f456…6083
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 0x982129521c…f19ba6
Audit this contract →
← previous block·next block →recent activity