pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,745,801
← previous block
next block →
recent activity
Analyzing
Block #89,745,801
13 transactions · 10 stateful · 2026-07-23 22:05:30 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,745,801
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc4d3a2…62bd
#2
0xb264ae19
#3
0xaf5e395a
· blocks 1
#4
0x47ab21…01d1
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#11
execOrders
#12
0xcf5e2743
#8
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x679795a0…a28c
0xfa32f9…f3f0
4 touches
1 conflict
0xb5ed555a…386f
0x3bd359…433a
2 touches
0 conflicts
0x7db59c24…a3fd
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
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
0x9194f4a340…d610b8
Audit this contract →
← previous block
·
next block →
recent activity