pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,190,503
← previous block
next block →
recent activity
Analyzing
Block #106,190,503
12 transactions · 11 stateful · 2026-09-19 13:35:47 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,190,503
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0x5acec890
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
sweepNative
#7
executeBatch
#8
transferWithAuthorization
#9
setData
#10
execOrders
· blocks 1
#2
matchOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce62e150…1e09
0x754704…b603
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcf570cc1…b19c
0x99c7a7…8bf0
4 touches
1 conflict
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0x5f0647bd…59b9
0x754704…b603
4 touches
1 conflict
0xa165a1e5…67be
0x754704…b603
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0xce62e15029…aa1e09
Audit this contract →
← previous block
·
next block →
recent activity