← previous blocknext block →recent activity
Analyzing
Block #89,415,905
18 transactions · 16 stateful · 2026-07-22 11:46:20 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,415,905 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x61ae437e…d136
0x34b655…2a6f
4 touches
1 conflict
0x6bfc7921…ffc8
0x34b655…2a6f
4 touches
1 conflict
0x6fa0f750…1fa4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity