pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,541,895
← previous block
next block →
recent activity
Analyzing
Block #96,541,895
11 transactions · 11 stateful · 2026-08-16 16:50:37 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,541,895
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
· blocks 1
#4
setData
#5
execOrders
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d377781…e5af
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x06d16c08…0c24
0x34b655…2a6f
2 touches
0 conflicts
0x0dd7d6d8…3700
0x34b655…2a6f
2 touches
0 conflicts
0x16838830…6ab2
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x9ca6fa7bcd…f2aeb3
Audit this contract →
← previous block
·
next block →
recent activity