← previous blocknext block →recent activity
Analyzing
Block #89,600,160
24 transactions · 21 stateful · 2026-07-23 08:17:09 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #89,600,160 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w413w514w616w717w823w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb5a47a02…d364
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe9991812…e391
0x34b655…2a6f
6 touches
3 conflicts
0xf7676b34…7209
0x34b655…2a6f
6 touches
3 conflicts
0x459cbb60…8957
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity