← previous blocknext block →recent activity
Analyzing
Block #89,770,435
14 transactions · 14 stateful · 2026-07-24 00:09:53 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,770,435 · 14 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
2w03w14w27w38w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2089dcc1…8f89
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xbce969bb…8007
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf6
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
4 touches
1 conflict
0x1321736a…43e3
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 0x2089dcc1cd…558f89
Audit this contract →
← previous block·next block →recent activity