pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,408,157
← previous block
next block →
recent activity
Analyzing
Block #106,408,157
14 transactions · 12 stateful · 2026-09-20 07:51:13 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,408,157
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0xab083028
#5
0x59558d29
#6
setData
· blocks 1
#8
execFwdPositionOpsV2
#9
matchOrders
#10
execOrders
#11
0xed82b078
#12
execOrders
#13
execOrders
#2
matchOrders
#7
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
0x363d5ac3…a29d
0x99c7a7…8bf0
4 touches
1 conflict
0x628e0d85…2e5c
0x99c7a7…8bf0
4 touches
1 conflict
0x8401a9f1…e868
0x754704…b603
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x524f0872…0d12
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
0x15c6ded916…e248e7
Audit this contract →
← previous block
·
next block →
recent activity