pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,020,037
← previous block
next block →
recent activity
Analyzing
Block #102,020,037
13 transactions · 12 stateful · 2026-09-04 22:33:27 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,020,037
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrders
#4
updatePrices
#5
0xab083028
#6
execOrders
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0xed82b078
#12
0x6a9b47af
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27c8497b…dcc4
0x754704…b603
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
4 touches
1 conflict
0xf4d134b9…d866
0x754704…b603
4 touches
1 conflict
0x1a489fe9…adcd
0x99c7a7…8bf0
4 touches
1 conflict
0xc48bb6d2…c376
0x99c7a7…8bf0
4 touches
1 conflict
0x1dc71894…1884
0x34b655…2a6f
2 touches
0 conflicts
0x21dc48d1…f395
0x34b655…2a6f
2 touches
0 conflicts
0x2f17174f…68b4
0x34b655…2a6f
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
0x27c8497bfa…65dcc4
Audit this contract →
← previous block
·
next block →
recent activity