← previous blocknext block →recent activity
Analyzing
Block #86,632,293
14 transactions · 13 stateful · 2026-07-09 13:29:28 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,632,293 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a9a1df9…6b66
0x34b655…2a6f
4 touches
1 conflict
0x2c2291e6…3e9d
0x34b655…2a6f
4 touches
1 conflict
0x3c3621c7…3e11
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x4b24f8b0…0368
0x34b655…2a6f
4 touches
1 conflict
0x589c04b7…6d97
0x34b655…2a6f
4 touches
1 conflict
0x6c7d4ae1…7bd3
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
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
1 conflict on slot 0x0a9a1df9eb…306b66
Audit this contract →
← previous block·next block →recent activity