pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,972,053
← previous block
next block →
recent activity
Analyzing
Block #101,972,053
11 transactions · 11 stateful · 2026-09-04 18:30:07 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,972,053
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
exactInputSingle
#3
exactInputSingle
#4
matchOrders
· blocks 1
#6
execOrders
· blocks 1
#7
0x59558d29
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#5
matchOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0xda18212c…b8b6
0x34b655…2a6f
4 touches
1 conflict
0xa6eca5ba…4390
0x754704…b603
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0x75a77817…b0ed
0x99c7a7…8bf0
4 touches
1 conflict
0x6780777a…9fb1
0x99c7a7…8bf0
4 touches
1 conflict
0x6f2dd36d…966d
0x8f415d…5241
3 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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
0xf96d61f88d…998fd8
Audit this contract →
← previous block
·
next block →
recent activity