pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,479,270
← previous block
next block →
recent activity
Analyzing
Block #102,479,270
11 transactions · 11 stateful · 2026-09-06 13:20:35 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,479,270
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0x59558d29
#3
transferWithAuthorization
· blocks 1
#5
setData
#6
execFwdPositionOpsV2
#7
0x57368ddf
#8
execFwdPositionOpsV2
#9
0x6a9d68a7
#10
execOrders
#4
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15a000bf…7425
0x1c8a33…d316
2 touches
0 conflicts
0x161acd64…ddeb
0x1c8a33…d316
2 touches
0 conflicts
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x261cbea7…e35d
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
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity