← previous blocknext block →recent activity
Analyzing
Block #89,526,686
22 transactions · 16 stateful · 2026-07-23 00:06:31 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,526,686 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w411w513w016w219w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x427f51fd…bd80
0x34b655…2a6f
4 touches
1 conflict
0x4fe9ce2c…91ce
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
0x34b655…2a6f
4 touches
1 conflict
0x576801fc…f80b
0x34b655…2a6f
4 touches
1 conflict
0x5d77346a…863a
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity