← previous blocknext block →recent activity
Analyzing
Block #86,925,397
22 transactions · 16 stateful · 2026-07-10 22:09:11 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,925,397 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w111w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6dcef4f…39dd
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0xb2e75fae…f11d
0x34b655…2a6f
4 touches
1 conflict
0x15b254ac…664f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xc6dcef4ffa…3039dd
Audit this contract →
← previous block·next block →recent activity