pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,353,105
← previous block
next block →
recent activity
Analyzing
Block #84,353,105
19 transactions · 13 stateful · 2026-06-29 00:06:19 UTC
Parallelism
95
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,353,105
· 19 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0xccf50a51
#7
0xccf50a51
#8
execPerpOps
#9
0x98717539
#10
execFwdPositionOps
#11
0xed82b078
#12
execFwdPositionOps
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#15
0x6a41b773
#16
setData
#17
0x21a24d…bfd8
#18
execOrders
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…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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