pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,447,035
← previous block
next block →
recent activity
Analyzing
Block #86,447,035
15 transactions · 12 stateful · 2026-07-08 16:49:36 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,447,035
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
multicall
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
executeBatch
#5
0x3f5c179b
#6
0xc5a04723
#7
execOrders
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
0x6a4e8018
#11
setData
#12
0xcfc2cf…4306
#13
0x67119a…501a
#14
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
0x00000000…000a
0x05a5a9…41ba
2 touches
0 conflicts
0x00000000…000b
0x05a5a9…41ba
2 touches
0 conflicts
0x00000000…000a
0x07dceb…4638
2 touches
0 conflicts
0x00000000…0014
0x07dceb…4638
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x1d10e771…bb26
0x3bd359…433a
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