pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,155,912
← previous block
next block →
recent activity
Analyzing
Block #95,155,912
20 transactions · 18 stateful · 2026-08-11 20:24:03 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
#95,155,912
· 20 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
execPerpOps
#3
execPerpOps
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
setData
#7
execFwdPositionOps
#8
CreateMemory
#9
CreateMemory
#10
CreateMemory
#11
CreateMemory
#12
CreateMemory
#13
CreateMemory
#14
CreateMemory
#15
CreateMemory
#16
CreateMemory
#17
CreateMemory
#18
execFwdPositionOps
#19
0x6a7b855b
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
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x288b2ecd…bcab
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