pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,707,731
← previous block
next block →
recent activity
Analyzing
Block #95,707,731
10 transactions · 10 stateful · 2026-08-13 18:53:56 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,707,731
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#6
0xed82b078
#7
0xed82b078
#8
setData
#9
execOrders
#4
execFwdPositionOpsV2
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe2ca9bf2…8da8
0x34b655…2a6f
4 touches
1 conflict
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0xf6937c39…e9fa
0x34b655…2a6f
4 touches
1 conflict
0x08db6fa4…88a0
0x34b655…2a6f
2 touches
0 conflicts
0x1fa4bbc6…20ea
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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
0x7c0bdc5473…099dde
Audit this contract →
← previous block
·
next block →
recent activity