← previous blocknext block →recent activity
Analyzing
Block #88,139,729
23 transactions · 17 stateful · 2026-07-16 13:30:35 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,139,729 · 23 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
1w02w19w011w012w113w214w115w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x50a31992…7cba
0x34b655…2a6f
6 touches
3 conflicts
0x5a2f7e74…189d
0x34b655…2a6f
4 touches
1 conflict
0x853675a4…4ab4
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0xb19c91c0…62c5
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity