pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,746,985
← previous block
next block →
recent activity
Analyzing
Block #95,746,985
10 transactions · 10 stateful · 2026-08-13 22:11:40 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,746,985
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
execFwdPositionOpsV2
#4
placeAndExecuteMarketBuy
· blocks 1
#6
0x94defb17
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#2
execFwdPositionOpsV2
#5
placeAndExecuteMarketSell
#7
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d28e45…760b
0x968279…9342
4 touches
1 conflict
0x60ea44fe…fb21
0x968279…9342
4 touches
1 conflict
0x60ea44fe…fb22
0x968279…9342
4 touches
1 conflict
0x60ea44fe…fb25
0x968279…9342
4 touches
1 conflict
0x60ea44fe…fb26
0x968279…9342
4 touches
1 conflict
0x60ea44fe…fb27
0x968279…9342
4 touches
1 conflict
0xa6d28e45…7608
0x968279…9342
4 touches
1 conflict
0xa6d28e45…7609
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
0xa6d28e4546…0c760b
Audit this contract →
← previous block
·
next block →
recent activity