pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,986,598
← previous block
next block →
recent activity
Analyzing
Block #95,986,598
10 transactions · 7 stateful · 2026-08-14 18:17:11 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,986,598
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
exactInputSingle
#3
redeemDelegations
#5
0x94defb17
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#4
execFwdPositionOpsV2
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37b3ff83…b8ad
0x968279…9342
4 touches
1 conflict
0x36fa1b1c…0968
0x968279…9342
4 touches
1 conflict
0x36fa1b1c…0969
0x968279…9342
4 touches
1 conflict
0x36fa1b1c…096b
0x968279…9342
4 touches
1 conflict
0x37b3ff83…b8a6
0x968279…9342
4 touches
1 conflict
0x37b3ff83…b8a7
0x968279…9342
4 touches
1 conflict
0x37b3ff83…b8aa
0x968279…9342
4 touches
1 conflict
0x37b3ff83…b8ab
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x37b3ff8358…a3b8ad
Audit this contract →
← previous block
·
next block →
recent activity