← previous blocknext block →recent activity
Analyzing
Block #88,158,100
21 transactions · 18 stateful · 2026-07-16 15:33:40 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,158,100 · 21 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
1w04w15w26w07w09w110w212w313w414w215w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0xd34b5587…cc86
0x34b655…2a6f
6 touches
3 conflicts
0xd50d8366…df9c
0x34b655…2a6f
6 touches
3 conflicts
0xe741c135…25a9
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity