pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,742,693
← previous block
next block →
recent activity
Analyzing
Block #82,742,693
16 transactions · 10 stateful · 2026-06-21 12:58:07 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
#82,742,693
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
execOrders
#11
modifyLiquidities
#12
0x6a37e057
#13
setData
#14
execOrders
#15
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4963015d…5715
0x188d58…ea8e
2 touches
0 conflicts
0x4963015d…5716
0x188d58…ea8e
2 touches
0 conflicts
0x7193f532…346d
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba62
0x188d58…ea8e
2 touches
0 conflicts
0xff6522dd…0309
0x188d58…ea8e
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