← previous blocknext block →recent activity
Analyzing
Block #89,739,016
10 transactions · 10 stateful · 2026-07-23 21:31:11 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,739,016 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x3b8eab7e…cc7b
0x34b655…2a6f
3 touches
1 conflict
0x085e35d2…8d20
0x34b655…2a6f
2 touches
0 conflicts
0x1549c910…9d20
0x34b655…2a6f
2 touches
0 conflicts
0x194be77e…58ae
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 0x313d3d93fa…ff4aa2
Audit this contract →
← previous block·next block →recent activity