← previous blocknext block →recent activity
Analyzing
Block #88,360,169
24 transactions · 21 stateful · 2026-07-17 14:06:02 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,360,169 · 24 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
2w03w14w08w09w111w212w313w414w015w116w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf24a351c…441f
0x34b655…2a6f
6 touches
3 conflicts
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x455ce975…e282
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
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
3 conflicts on slot 0xc7954a6095…b3d294
Audit this contract →
← previous block·next block →recent activity