← previous blocknext block →recent activity
Analyzing
Block #86,799,500
24 transactions · 20 stateful · 2026-07-10 08:07:18 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,799,500 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w18w09w110w211w312w313w414w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xee5a28ec…7261
0x34b655…2a6f
8 touches
6 conflicts
0xa3718bd2…e4c8
0xd32edf…ff58
7 touches
6 conflicts
0xe90b7bce…c2e0
0xfa32f9…f3f0
6 touches
3 conflicts
0x8bc5abbb…a84e
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity