← previous blocknext block →recent activity
Analyzing
Block #89,711,233
12 transactions · 12 stateful · 2026-07-23 19:10:52 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,711,233 · 12 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
4w05w06w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0x3da553b9…d669
0x34b655…2a6f
6 touches
3 conflicts
0x9932c6d5…0e66
0x0a2fbf…29b1
4 touches
1 conflict
0x9932c6d5…0e69
0x0a2fbf…29b1
4 touches
1 conflict
0x0da9d4d1…837f
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x5fde497131…e8aac9
Audit this contract →
← previous block·next block →recent activity