pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,213,259
← previous block
next block →
recent activity
Analyzing
Block #103,213,259
12 transactions · 11 stateful · 2026-09-09 03:04:54 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
#103,213,259
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
0x5acec890
· blocks 1
#5
0x5acec890
#6
executeBatch
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
exactInputSingle
#11
0xc7068c7b
#4
0x5acec890
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x90c25f46…de91
0x34b655…2a6f
2 touches
0 conflicts
0x21088989…ba5c
0x34b655…2a6f
2 touches
0 conflicts
0x2ef849ce…ac81
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:
Perpl
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity