pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,008,073
← previous block
next block →
recent activity
Analyzing
Block #92,008,073
12 transactions · 10 stateful · 2026-07-31 20:11:31 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,008,073
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#5
execOrders
#6
execOrders
#7
0x6a6d01eb
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#4
mergePositions
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x431fa96d…6ac0
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
4 touches
1 conflict
0x6d8bf82a…3f56
0x99c7a7…8bf0
4 touches
1 conflict
0x7f03e539…f4cc
0x754704…b603
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
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
0x431fa96d88…fb6ac0
Audit this contract →
← previous block
·
next block →
recent activity