pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,316,200
← previous block
next block →
recent activity
Analyzing
Block #80,316,200
12 transactions · 10 stateful · 2026-06-10 07:16:54 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,316,200
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
updatePriceFeedsIfNecessary
#9
0x3f5c179b
#10
0x6a290fdd
#11
0xc7e3ec2c
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
0x1159a409…4cce
0x34b655…2a6f
2 touches
0 conflicts
0x20879eeb…3b5b
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0x88c56519…b0e8
0x34b655…2a6f
2 touches
0 conflicts
0x90f07a4f…d932
0x34b655…2a6f
2 touches
0 conflicts
0xd7df7783…ccfd
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