pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,014,485
← previous block
next block →
recent activity
Analyzing
Block #92,014,485
13 transactions · 11 stateful · 2026-07-31 20:43:46 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,014,485
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x94defb17
· blocks 1
#5
execFwdPositionOps
#6
execOrders
#7
execOrders
#8
setData
#9
execOrders
#10
0x59558d29
#11
0xc7e3ec2c
#12
0xc7e3ec2c
#4
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x4863e718…b481
0x7b9256…1fb2
4 touches
1 conflict
0x4863e718…b482
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0dad
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0dae
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0db1
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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:
USDC (USDC)
1 conflict on slot
0xe1f61186c5…67e2f8
Audit this contract →
← previous block
·
next block →
recent activity