pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,531,402
← previous block
next block →
recent activity
Analyzing
Block #95,531,402
12 transactions · 11 stateful · 2026-08-13 04:06:17 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,531,402
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
· blocks 1
#3
dagSwapByOrderId
#4
0x000000b2
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
executeBatch
#9
execFwdPositionOps
#10
0x6a7d4330
#11
setData
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4aa2ec78…227d
0xa6afd3…d132
3 touches
1 conflict
0x1c5fec93…2b88
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0xc6b1d98106…cc1be2
Audit this contract →
← previous block
·
next block →
recent activity