pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,282,150
← previous block
next block →
recent activity
Analyzing
Block #96,282,150
12 transactions · 11 stateful · 2026-08-15 19:03:56 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,282,150
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
execOrder
· blocks 1
#4
updatePrices
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#7
updateDataFeedsValuesPartial
#9
handleOps
#10
transfer
#11
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x60d732ff…3b8a
0x34b655…2a6f
4 touches
1 conflict
0x98fc2168…1366
0x34b655…2a6f
4 touches
1 conflict
0xba0aa618…04aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f8
0x34b655…2a6f
2 touches
0 conflicts
0x3dae5ee1…721b
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity