← previous blocknext block →recent activity
Analyzing
Block #88,185,193
16 transactions · 15 stateful · 2026-07-16 18:35:23 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,185,193 · 16 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
1w02w14w15w26w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9da42530…1c86
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x70e3da66…674a
0x34b655…2a6f
6 touches
3 conflicts
0x5a7eb2ab…75a0
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2f461725…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x33c7a9e0…4810
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
15 conflicts on slot 0x9da425306f…1b1c86
Audit this contract →
← previous block·next block →recent activity