← previous blocknext block →recent activity
Analyzing
Block #89,385,519
25 transactions · 21 stateful · 2026-07-22 08:23:10 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,385,519 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w213w214w315w416w522w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xae1101fb…0e7f
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity