← previous blocknext block →recent activity
Analyzing
Block #88,092,174
23 transactions · 22 stateful · 2026-07-16 08:12:26 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,092,174 · 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
1w02w03w14w05w110w011w114w117w018w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e17e82a…9748
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x982900c0…d7a7
0x34b655…2a6f
6 touches
3 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
4 touches
1 conflict
0x45afe05e…1607
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa0dc0d08…d3f0
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 0x7e17e82a8c…109748
Audit this contract →
← previous block·next block →recent activity