← previous blocknext block →recent activity
Analyzing
Block #89,735,364
15 transactions · 14 stateful · 2026-07-23 21:12:43 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,735,364 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w110w212w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e0e8837…2e59
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc6b604e6…5152
0x34b655…2a6f
6 touches
3 conflicts
0x3fed3b54…77f3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa58a5f97…2e6b
0x34b655…2a6f
4 touches
1 conflict
0xa8a53716…3386
0x34b655…2a6f
4 touches
1 conflict
0xbe33297f…2f58
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 0x6e0e883716…732e59
Audit this contract →
← previous block·next block →recent activity