pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,513,111
← previous block
next block →
recent activity
Analyzing
Block #86,513,111
14 transactions · 10 stateful · 2026-07-09 00:11:10 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,513,111
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
0x3f5c179b
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
transfer
#11
setData
#12
0x905153…eb39
#13
0x40e8cb…39aa
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x05835d82…9130
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…caca
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…cacb
0x34b655…2a6f
2 touches
0 conflicts
0x3cb231a9…887d
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.
← previous block
·
next block →
recent activity