pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,834,584
← previous block
next block →
recent activity
Analyzing
Block #86,834,584
10 transactions · 9 stateful · 2026-07-10 12:02:02 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,834,584
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
0x6a50dfb2
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xcaf5a5ac…09f0
0x34b655…2a6f
4 touches
1 conflict
0x3c610031…a65e
0x34b655…2a6f
2 touches
0 conflicts
0x650e90b3…213c
0x34b655…2a6f
2 touches
0 conflicts
0x650e90b3…213d
0x34b655…2a6f
2 touches
0 conflicts
0x7fc0a229…9d4a
0x34b655…2a6f
2 touches
0 conflicts
0x87646412…80a4
0x34b655…2a6f
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity