pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,666,068
← previous block
next block →
recent activity
Analyzing
Block #96,666,068
16 transactions · 11 stateful · 2026-08-17 03:15:09 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,666,068
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x4f819052
#2
execute
#3
0x50a0b275
#4
main_all
#5
0xa96df62f
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x5acec890
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
0x3f5c179b
#13
executeBatch
#14
execOrders
#15
setData
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
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0xe60cff44…1b50
0x57ea24…2cec
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