pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,986,717
← previous block
next block →
recent activity
Analyzing
Block #95,986,717
19 transactions · 17 stateful · 2026-08-14 18:17:47 UTC
Parallelism
89
/100
Blocked
6
%
Avg conflicts / tx
0.05
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,986,717
· 19 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5acec890
#4
execFwdPositionOpsV2
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
approve
#9
approve
#10
approve
#11
approve
#12
approve
#13
approve
#14
approve
#15
approve
#16
approve
#17
approve
#18
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e4
0x34b655…2a6f
2 touches
0 conflicts
0x34933aba…06e5
0x34b655…2a6f
2 touches
0 conflicts
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x46ee3c65…4ab8
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
0x6d1b72eefe…416b78
Audit this contract →
← previous block
·
next block →
recent activity