← previous blocknext block →recent activity
Analyzing
Block #89,769,795
11 transactions · 10 stateful · 2026-07-24 00:06:40 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,769,795 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w37w410w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x87f29f74…7c8b
0x34b655…2a6f
4 touches
1 conflict
0x1d5181ef…7074
0x34b655…2a6f
4 touches
1 conflict
0xaedc3dd6…3c3b
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity