← previous blocknext block →recent activity
Analyzing
Block #89,675,235
13 transactions · 12 stateful · 2026-07-23 16:09:14 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,675,235 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x572f121e…964f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x13981d20…e8b5
0x34b655…2a6f
2 touches
0 conflicts
0x13f8c55c…3061
0x34b655…2a6f
2 touches
0 conflicts
0x2a1a17d1…82c0
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
1 conflict on slot 0x572f121e13…6d964f
Audit this contract →
← previous block·next block →recent activity