← previous blocknext block →recent activity
Analyzing
Block #89,855,327
14 transactions · 12 stateful · 2026-07-24 07:18:09 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,855,327 · 14 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
2w03w14w25w36w07w48w59w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641e
0x34b655…2a6f
8 touches
6 conflicts
0xd51e027e…7c31
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7085
0x34b655…2a6f
6 touches
3 conflicts
0x65c50a7f…f491
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity