pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,087,868
← previous block
next block →
recent activity
Analyzing
Block #96,087,868
11 transactions · 8 stateful · 2026-08-15 02:46:42 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,087,868
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
repayWithCollateral
#8
transfer
· blocks 1
#10
setData
#7
execFwdPositionOpsV2
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x242d7508…7152
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6571
0x34b655…2a6f
2 touches
0 conflicts
0x40a9339c…6572
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
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
0x83f3d32000…25fb59
Audit this contract →
← previous block
·
next block →
recent activity