pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,610,336
← previous block
next block →
recent activity
Analyzing
Block #96,610,336
13 transactions · 11 stateful · 2026-08-16 22:34:51 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,610,336
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrder
#2
0x5acec890
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
forward
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#12
0xb3fd51…4299
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
0x0e830941…e6a7
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2d651956…12e8
0x34b655…2a6f
2 touches
0 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
2 touches
0 conflicts
0x66025912…9a35
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