pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,919,932
← previous block
next block →
recent activity
Analyzing
Block #86,919,932
11 transactions · 10 stateful · 2026-07-10 21:32:36 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,919,932
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
executeBatch
#6
execFwdPositionOps
#8
0x6a51656b
#9
setData
#10
execOrders
#2
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfffe583a…9130
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa644c79b…694d
0x34b655…2a6f
4 touches
1 conflict
0xb104db11…2208
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae35
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1b0f031c…fec9
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
1 conflict on slot
0xfffe583a09…d59130
Audit this contract →
← previous block
·
next block →
recent activity