pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,976,743
← previous block
next block →
recent activity
Analyzing
Block #95,976,743
8 transactions · 6 stateful · 2026-08-14 17:27:37 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,976,743
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
repayWithCollateral
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
batchUpdatePrice
#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
0xd6255b52…69e7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x1244b105…8e9c
0x34b655…2a6f
4 touches
1 conflict
0x1f0fb1c9…6968
0x34b655…2a6f
4 touches
1 conflict
0x34933aba…06e4
0x34b655…2a6f
4 touches
1 conflict
0x990bf0c1…a307
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x03b80be8…1214
0x34b655…2a6f
3 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:
Perpl
1 conflict on slot
0xd6255b5277…7f69e7
Audit this contract →
← previous block
·
next block →
recent activity