← previous blocknext block →recent activity
Analyzing
Block #89,698,768
7 transactions · 7 stateful · 2026-07-23 18:08:04 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,698,768 · 7 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
1w02w13w25w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x217dc350…0a0f
0x34b655…2a6f
2 touches
0 conflicts
0x2794fd34…c82f
0x34b655…2a6f
2 touches
0 conflicts
0x36e357c3…d325
0x34b655…2a6f
2 touches
0 conflicts
0x39723d07…4abb
0x34b655…2a6f
2 touches
0 conflicts
0x39723d07…4abc
0x34b655…2a6f
2 touches
0 conflicts
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity