pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,648,449
← previous block
next block →
recent activity
Analyzing
Block #95,648,449
15 transactions · 13 stateful · 2026-08-13 13:55:01 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,648,449
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x3f5c179b
#8
execOrders
#9
execFwdPositionOps
#10
0xed82b078
#11
0x6a7dcd2c
#12
setData
#13
0x59558d29
#14
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
0x261cbea7…e35d
0x34b655…2a6f
2 touches
0 conflicts
0x261cbea7…e35e
0x34b655…2a6f
2 touches
0 conflicts
0x2bd66f15…8cee
0x34b655…2a6f
2 touches
0 conflicts
0x34a3064b…1869
0x34b655…2a6f
2 touches
0 conflicts
0x36a76bd2…1fb0
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