← previous blocknext block →recent activity
Analyzing
Block #89,405,215
30 transactions · 24 stateful · 2026-07-22 10:34:53 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,405,215 · 30 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
3w04w111w012w115w225w126w227w328w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4681609f…6493
0x34b655…2a6f
6 touches
3 conflicts
0x1750b664…8fa2
0x34b655…2a6f
6 touches
3 conflicts
0x346baa70…d21e
0x34b655…2a6f
4 touches
1 conflict
0x382f1ad4…61d5
0x34b655…2a6f
4 touches
1 conflict
0x419e8aec…c769
0x34b655…2a6f
4 touches
1 conflict
0x5bdaf996…8fef
0x34b655…2a6f
4 touches
1 conflict
0x69710772…c966
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity