← previous blocknext block →recent activity
Analyzing
Block #89,384,444
13 transactions · 11 stateful · 2026-07-22 08:15:59 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,384,444 · 13 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
4w06w09w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496ff651…1310
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x79bdf655…91f2
0x34b655…2a6f
4 touches
1 conflict
0xd1193b94…1930
0x34b655…2a6f
4 touches
1 conflict
0xf2b4052c…ec8b
0x34b655…2a6f
4 touches
1 conflict
0x508bbf1b…fe95
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2fd48b4a…4d5a
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
3 conflicts on slot 0x496ff65132…401310
Audit this contract →
← previous block·next block →recent activity