← previous blocknext block →recent activity
Analyzing
Block #89,679,262
23 transactions · 16 stateful · 2026-07-23 16:29:41 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,679,262 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w012w116w117w218w319w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc948dbdc…199a
0x34b655…2a6f
6 touches
3 conflicts
0x59991669…58c6
0x34b655…2a6f
6 touches
3 conflicts
0x82290204…3db0
0x34b655…2a6f
5 touches
3 conflicts
0x43faf654…7e66
0x34b655…2a6f
4 touches
1 conflict
0x46a7d766…9797
0x34b655…2a6f
4 touches
1 conflict
0xa14714cd…69ef
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity