← previous blocknext block →recent activity
Analyzing
Block #89,378,609
16 transactions · 15 stateful · 2026-07-22 07:36:58 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,378,609 · 16 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
1w06w07w18w19w110w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1d68c976…b6e6
0x34b655…2a6f
6 touches
3 conflicts
0x7da56943…9753
0x34b655…2a6f
6 touches
3 conflicts
0x6e0e8837…2e59
0x34b655…2a6f
6 touches
3 conflicts
0xf2470d60…8a22
0x34b655…2a6f
6 touches
3 conflicts
0x1bd69a6a…2b8a
0x34b655…2a6f
5 touches
3 conflicts
0x7c59a6a5…6915
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity