← previous blocknext block →recent activity
Analyzing
Block #89,576,117
25 transactions · 20 stateful · 2026-07-23 05:36:39 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,576,117 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w210w313w414w416w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2b8d9898…d525
0x34b655…2a6f
6 touches
3 conflicts
0x9355efee…7bcd
0x34b655…2a6f
6 touches
3 conflicts
0x4ca81ae8…01d4
0x34b655…2a6f
4 touches
1 conflict
0x5df2b506…adeb
0x34b655…2a6f
4 touches
1 conflict
0x89cb60e7…6243
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity