pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,708,123
← previous block
next block →
recent activity
Analyzing
Block #95,708,123
10 transactions · 7 stateful · 2026-08-13 18:55:54 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,708,123
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
execOrders
#4
execFwdPositionOpsV2
· blocks 1
#5
updateDataFeedsValuesPartial
#7
batchUpdate
#8
execFwdPositionOpsV2
#9
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2142951…6af0
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x078a9868…7a1f
0x34b655…2a6f
2 touches
0 conflicts
0x11df48c1…f028
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x2bb41ab1…e5e7
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d8
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
0xe2142951fb…326af0
Audit this contract →
← previous block
·
next block →
recent activity