pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,288,557
← previous block
next block →
recent activity
Analyzing
Block #84,288,557
18 transactions · 7 stateful · 2026-06-28 16:56:12 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,288,557
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrder
#2
execOrder
#3
execOrder
#4
execOrder
#5
execOrder
#6
execOrder
#7
execOrder
#8
execOrder
#9
execOrder
#10
execOrder
#11
updateDataFeedsValuesPartial
#12
updatePrices
#13
setData
#14
execFwdPositionOps
#15
execFwdPositionOps
#16
0x9643e4…b08f
#17
0x153fae…e6ac
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
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x01cc77f6…4f6f
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad05
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad07
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