pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,680,699
← previous block
next block →
recent activity
Analyzing
Block #86,680,699
8 transactions · 7 stateful · 2026-07-09 18:53:59 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,680,699
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
swapExactIn
#3
0x0f6795d9
· blocks 1
#5
setData
#6
0xb8024e8c
#7
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5decd02…dbf4
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6083af24…a0df
0x34b655…2a6f
2 touches
0 conflicts
0x143dba04…1b98
0xb1dbf0…c0d3
2 touches
0 conflicts
0x1e451306…7993
0xb1dbf0…c0d3
2 touches
0 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
1 conflict on slot
0xc5decd02b3…07dbf4
Audit this contract →
← previous block
·
next block →
recent activity