← previous blocknext block →recent activity
Analyzing
Block #89,830,316
21 transactions · 20 stateful · 2026-07-24 05:12:04 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,830,316 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w210w011w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x17b6918d…4437
0x0a2fbf…29b1
4 touches
1 conflict
0x17b6918d…4438
0x0a2fbf…29b1
4 touches
1 conflict
0x17b6918d…443b
0x0a2fbf…29b1
4 touches
1 conflict
0x4c489c36…7a70
0x0a2fbf…29b1
4 touches
1 conflict
0x4c489c36…7a71
0x0a2fbf…29b1
4 touches
1 conflict
0x4c489c36…7a72
0x0a2fbf…29b1
4 touches
1 conflict
0x0733be30…112f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity