← previous blocknext block →recent activity
Analyzing
Block #88,183,966
21 transactions · 17 stateful · 2026-07-16 18:27:07 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,183,966 · 21 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
1w04w15w06w19w210w311w112w413w514w617w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
6 touches
3 conflicts
0x9001f549…089d
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 0xf195ad96b6…00e0c3
Audit this contract →
← previous block·next block →recent activity