pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,431,727
← previous block
next block →
recent activity
Analyzing
Block #92,431,727
11 transactions · 10 stateful · 2026-08-02 07:42:10 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,431,727
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#5
placeAndExecuteMarketBuy
#7
0x6a6ef54a
#8
setData
#9
execOrders
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x16619921…0b9d
0x34b655…2a6f
2 touches
0 conflicts
0x1d9699cc…3066
0x34b655…2a6f
2 touches
0 conflicts
0x27b96981…ef48
0x34b655…2a6f
2 touches
0 conflicts
0x28466a40…ad26
0x34b655…2a6f
2 touches
0 conflicts
0x3516e431…c618
0x34b655…2a6f
2 touches
0 conflicts
0x37c70870…b872
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
0x91b0f8edc5…b76bd7
Audit this contract →
← previous block
·
next block →
recent activity