pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,809,232
← previous block
next block →
recent activity
Analyzing
Block #95,809,232
8 transactions · 7 stateful · 2026-08-14 03:24:43 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,809,232
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x5acec890
· blocks 1
#5
placeAndExecuteMarketSell
#6
execFwdPositionOpsV2
#7
setData
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8cd993…5c11
0x34b655…2a6f
4 touches
1 conflict
0x4bf59d22…00de
0x34b655…2a6f
4 touches
1 conflict
0x08ff2573…8168
0x34b655…2a6f
2 touches
0 conflicts
0x128664cc…be3d
0x34b655…2a6f
2 touches
0 conflicts
0x2464f36f…724c
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
0x34b655…2a6f
2 touches
0 conflicts
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x4efae872…6aa8
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot
0xfc8cd99357…7e5c11
Audit this contract →
← previous block
·
next block →
recent activity