← previous blocknext block →recent activity
Analyzing
Block #86,675,291
22 transactions · 19 stateful · 2026-07-09 18:17:54 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,675,291 · 22 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
1w04w05w16w29w110w011w112w213w214w315w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xada5ad75…1d24
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2fa2e180…87a9
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x363a4317…87d2
0x34b655…2a6f
6 touches
3 conflicts
0x4572c9a0…5cf9
0x34b655…2a6f
6 touches
3 conflicts
0x4c902bce…2b75
0x34b655…2a6f
6 touches
3 conflicts
0x56b7d327…045d
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xada5ad75a3…de1d24
Audit this contract →
← previous block·next block →recent activity