← previous blocknext block →recent activity
Analyzing
Block #89,555,921
17 transactions · 16 stateful · 2026-07-23 03:21:44 UTC
Parallelism
71/100
Blocked
25%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,555,921 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w110w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf1a0b65…3582
0x34b655…2a6f
8 touches
6 conflicts
0xd6c0349d…05b0
0x34b655…2a6f
8 touches
6 conflicts
0x0b898c74…0cc9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x28448f74…4f06
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xdf1a0b6564…4e3582
Audit this contract →
← previous block·next block →recent activity