← previous blocknext block →recent activity
Analyzing
Block #89,769,654
22 transactions · 20 stateful · 2026-07-24 00:05:57 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,769,654 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w110w214w319w020w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5c75a87…787c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x4bb0bfb0…8f11
0x34b655…2a6f
2 touches
0 conflicts
0x71806e15…2893
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xf5c75a873f…d1787c
Audit this contract →
← previous block·next block →recent activity