pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,167,058
← previous block
next block →
recent activity
Analyzing
Block #86,167,058
11 transactions · 9 stateful · 2026-07-07 09:39:42 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,167,058
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
execFwdPositionOps
· blocks 2
#5
forward
#7
setData
#8
execOrders
#9
execOrders
#10
0xc7e3ec2c
#4
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x040f5870…c505
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x24549322…9e89
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x390da1b0…5cdb
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
0x0950060282…6794e9
Audit this contract →
← previous block
·
next block →
recent activity