← previous blocknext block →recent activity
Analyzing
Block #89,597,356
20 transactions · 17 stateful · 2026-07-23 07:58:27 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,597,356 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w28w09w110w215w316w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1cc9519…84c1
0x34b655…2a6f
8 touches
6 conflicts
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0x9fd37234…2731
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe819ad9d…3e2a
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xf1cc9519e3…fe84c1
Audit this contract →
← previous block·next block →recent activity