← previous blocknext block →recent activity
Analyzing
Block #89,518,839
24 transactions · 19 stateful · 2026-07-22 23:14:03 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,518,839 · 24 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
2w06w07w18w29w114w216w322w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4527790…c282
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8a7af3fd…72a6
0x34b655…2a6f
6 touches
3 conflicts
0xaf981b7d…ceed
0x34b655…2a6f
6 touches
3 conflicts
0xb7526c61…87f2
0x34b655…2a6f
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x539ecb5b…871b
0x34b655…2a6f
4 touches
1 conflict
0x5bf925a9…22fe
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
6 conflicts on slot 0xb4527790c7…f9c282
Audit this contract →
← previous block·next block →recent activity