← previous blocknext block →recent activity
Analyzing
Block #86,768,157
20 transactions · 15 stateful · 2026-07-10 04:38:06 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,768,157 · 20 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
1w02w14w06w18w19w110w211w312w413w017w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x119694b6…b8dc
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x7148d477…63e4
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
10 conflicts on slot 0x119694b61e…e0b8dc
Audit this contract →
← previous block·next block →recent activity