pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,559,662
← previous block
next block →
recent activity
Analyzing
Block #95,559,662
10 transactions · 8 stateful · 2026-08-13 06:28:25 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,559,662
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
verifyOracleProofV2
#6
execFwdPositionOps
#7
0x6a7d6481
#8
setData
#9
0x59558d29
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x81d2ebf9…2915
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…a0ca
0x16f70c…c3dd
2 touches
0 conflicts
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x06e9e386…506d
0x34b655…2a6f
2 touches
0 conflicts
0x1088dfef…9fc2
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
0xe21234e760…98bded
Audit this contract →
← previous block
·
next block →
recent activity