pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,134,027
← previous block
next block →
recent activity
Analyzing
Block #94,134,027
10 transactions · 7 stateful · 2026-08-08 06:26:44 UTC
Parallelism
80
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,134,027
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
exactInputSingle
#4
execFwdPositionOps
· blocks 2
#6
placeAndExecuteMarketSell
#7
setData
#9
0xc7e3ec2c
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4527790…c282
0x34b655…2a6f
4 touches
1 conflict
0x41c66186…229a
0x34b655…2a6f
4 touches
1 conflict
0x90a66fa7…9014
0x34b655…2a6f
4 touches
1 conflict
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x1347f8fa…31d4
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63b
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63c
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
0xb4527790c7…f9c282
Audit this contract →
← previous block
·
next block →
recent activity