pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,392,807
← previous block
next block →
recent activity
Analyzing
Block #106,392,807
12 transactions · 11 stateful · 2026-09-20 06:33:59 UTC
Parallelism
83
/100
Blocked
27
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,392,807
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0x0c7abd22
· blocks 1
#5
0x5acec890
· blocks 1
#7
setData
#8
exactInputSingle
#9
handleOps
#10
execOrders
· blocks 1
#2
matchOrders
#6
0x0c7abd22
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w0
6
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0x14b2b355…8ce5
0x99c7a7…8bf0
4 touches
1 conflict
0xc446711e…b7cb
0x99c7a7…8bf0
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x643fa4aa…a822
0x754704…b603
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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
0x73bb65fcbe…87650d
Audit this contract →
← previous block
·
next block →
recent activity