pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,525,890
← previous block
next block →
recent activity
Analyzing
Block #95,525,890
13 transactions · 12 stateful · 2026-08-13 03:38:33 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,525,890
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x6ad2e98b
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
withdraw
#6
execFwdPositionOps
#7
placeAndExecuteMarketSell
#8
0x94defb17
· blocks 1
#10
0x6a7d3cb1
#11
setData
#12
0x59558d29
#9
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04044955…08ac
0x968279…9342
4 touches
1 conflict
0x04044955…08ad
0x968279…9342
4 touches
1 conflict
0x04044955…08b0
0x968279…9342
4 touches
1 conflict
0x04044955…08b1
0x968279…9342
4 touches
1 conflict
0x04044955…08b3
0x968279…9342
4 touches
1 conflict
0xa96cffd1…f5e2
0x968279…9342
4 touches
1 conflict
0xa96cffd1…f5e3
0x968279…9342
4 touches
1 conflict
0xa96cffd1…f5e5
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
0x040449559b…4b08ac
Audit this contract →
← previous block
·
next block →
recent activity