pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,496,664
← previous block
next block →
recent activity
Analyzing
Block #96,496,664
18 transactions · 14 stateful · 2026-08-16 13:02:53 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
#96,496,664
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x5acec890
#2
withdraw
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
0x94defb17
#6
multicall
#7
execFwdPositionOpsV2
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
setData
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
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
0x2dd03fb9…6243
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
2 touches
0 conflicts
0x588380ee…0a5c
0x34b655…2a6f
2 touches
0 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
2 touches
0 conflicts
0x775bacba…73e5
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