pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,088,085
← previous block
next block →
recent activity
Analyzing
Block #96,088,085
8 transactions · 8 stateful · 2026-08-15 02:47:48 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,088,085
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
batchRequestPriceCallback
#2
execFwdPositionOpsV2
· blocks 1
#3
execFwdPositionOpsV2
#4
updateDataFeedsValuesPartial
#6
repayWithCollateral
#7
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2e2709…d023
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d21
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x62b13313…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x1dbd2210…7786
0x34b655…2a6f
3 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x5b30a6e6…b249
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
0x8a2e270979…ffd023
Audit this contract →
← previous block
·
next block →
recent activity