pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,200,397
← previous block
next block →
recent activity
Analyzing
Block #92,200,397
9 transactions · 8 stateful · 2026-08-01 12:18:47 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,200,397
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
0x94defb17
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
setData
#7
execOrders
#8
0xc7e3ec2c
#3
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x1547967f…bde9
0x7b9256…1fb2
4 touches
1 conflict
0x1547967f…bdea
0x7b9256…1fb2
4 touches
1 conflict
0xf214d5fe…2b90
0x7b9256…1fb2
4 touches
1 conflict
0xf214d5fe…2b91
0x7b9256…1fb2
4 touches
1 conflict
0xf214d5fe…2b94
0x7b9256…1fb2
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
0x177211e248…161c2d
Audit this contract →
← previous block
·
next block →
recent activity