← previous blocknext block →recent activity
Analyzing
Block #88,158,935
10 transactions · 9 stateful · 2026-07-16 15:39:15 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,158,935 · 10 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
1w02w13w04w26w37w49w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0090639e…243e
0x34b655…2a6f
6 touches
3 conflicts
0x095a2c84…6648
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9465204c…bf37
0x34b655…2a6f
6 touches
3 conflicts
0xdc54eb34…fe58
0x34b655…2a6f
6 touches
3 conflicts
0xbbfa7e14…98a3
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x0090639ed3…ab243e
Audit this contract →
← previous block·next block →recent activity