pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,976,640
← previous block
next block →
recent activity
Analyzing
Block #95,976,640
10 transactions · 7 stateful · 2026-08-14 17:27:06 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,976,640
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
· blocks 2
#3
execOrder
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#7
redeemDelegations
#9
setData
#6
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1cc1ec8e…be2f
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x750fb05c…0e99
0x34b655…2a6f
4 touches
1 conflict
0xc9eaa844…2344
0x34b655…2a6f
4 touches
1 conflict
0xcd6caad2…7929
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0xcd6caad2…792a
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x1cc1ec8e36…6abe2f
Audit this contract →
← previous block
·
next block →
recent activity