pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,442,744
← previous block
next block →
recent activity
Analyzing
Block #96,442,744
11 transactions · 9 stateful · 2026-08-16 08:31:36 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,442,744
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updatePrices
#4
forward
#5
updateDataFeedsValuesPartial
#6
updatePosition
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
0x61d59c2d
· blocks 1
#2
0xab083028
#10
swapExactTokensForTokens
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf3
0x77d53b…8080
4 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: Settlement / Helper
1 conflict on slot
0xbb97db90cd…304c93
Audit this contract →
← previous block
·
next block →
recent activity