pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,714,149
← previous block
next block →
recent activity
Analyzing
Block #95,714,149
13 transactions · 11 stateful · 2026-08-13 19:26:26 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
#95,714,149
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
artefact_keep
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
#4
0xb2d4797b
#5
0x3f5c179b
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
updateTemporalNumericValuesV1
#9
updateDataFeedsValuesPartial
#10
0x6a7e1ada
#11
setData
#12
0x61d59c2d
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
0x06906acd…e07e
0x34b655…2a6f
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x2ca3a7a0…e60d
0x34b655…2a6f
2 touches
0 conflicts
0x6000c10c…483d
0x34b655…2a6f
2 touches
0 conflicts
0x620b761c…270e
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