pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,431,416
← previous block
next block →
recent activity
Analyzing
Block #92,431,416
12 transactions · 10 stateful · 2026-08-02 07:40:36 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,431,416
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
metacall
#8
execOrders
#9
0x6a6ef4ec
#10
setData
#11
0x59558d29
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aa512ae…d2e0
0x754704…b603
4 touches
1 conflict
0x7f03e539…f4cc
0x754704…b603
4 touches
1 conflict
0xe50f87d9…047c
0x754704…b603
4 touches
1 conflict
0x69a550fe…7f87
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0002
0x91855e…ac7e
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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:
USDC (USDC)
1 conflict on slot
0x7aa512ae24…a4d2e0
Audit this contract →
← previous block
·
next block →
recent activity