pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,455,011
← previous block
next block →
recent activity
Analyzing
Block #86,455,011
14 transactions · 13 stateful · 2026-07-08 17:42:55 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,455,011
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
executeBatch
#8
updatePosition
#9
0x57368ddf
#10
execFwdPositionOps
#11
0x6a4e8c97
#12
0xd708c5d8
#13
setData
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x07cd00e0…6a34
0x065c9d…c394
2 touches
0 conflicts
0x0d2a41ea…c0aa
0x065c9d…c394
2 touches
0 conflicts
0x106a81c7…e505
0x065c9d…c394
2 touches
0 conflicts
0x19892d3e…7e21
0x065c9d…c394
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