pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,307,682
← previous block
next block →
recent activity
Analyzing
Block #96,307,682
12 transactions · 11 stateful · 2026-08-15 21:12:20 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,307,682
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
execFwdPositionOpsV2
· blocks 1
#7
0xb2d4797b
#8
updatePriceFeedsIfNecessary
#9
0x94defb17
· blocks 1
#11
setData
#6
execFwdPositionOpsV2
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf89542f…7531
0x968279…9342
4 touches
1 conflict
0xaf89542f…7534
0x968279…9342
4 touches
1 conflict
0xaf89542f…7535
0x968279…9342
4 touches
1 conflict
0xaf89542f…7537
0x968279…9342
4 touches
1 conflict
0x7ef4ba09…2a25
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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
0xaf89542f64…617531
Audit this contract →
← previous block
·
next block →
recent activity