← previous blocknext block →recent activity
Analyzing
Block #88,354,061
18 transactions · 17 stateful · 2026-07-17 13:24:44 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,354,061 · 18 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
2w03w16w27w310w411w012w013w114w315w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e914191…542c
0x34b655…2a6f
6 touches
3 conflicts
0x8e914191…542d
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd016ba14…8708
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8e3db883…fb9f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9d13199a…cae2
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 0x8e9141910b…b6542c
Audit this contract →
← previous block·next block →recent activity