← previous blocknext block →recent activity
Analyzing
Block #86,957,358
46 transactions · 39 stateful · 2026-07-11 01:42:41 UTC
Parallelism
70/100
Blocked
72%
Avg conflicts / tx
1.83
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,957,358 · 46 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w07w18w29w110w011w112w215w017w118w219w320w421w522w623w724w826w227w534w335w136w237w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x94de4d05…ad01
0x34b655…2a6f
8 touches
6 conflicts
0xb0446875…2b96
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
7 touches
6 conflicts
0x9216894f…5d86
0x34b655…2a6f
6 touches
3 conflicts
0x6d99ac64…0aa3
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed530c…d450
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity