pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,189,142
← previous block
next block →
recent activity
Analyzing
Block #106,189,142
10 transactions · 9 stateful · 2026-09-19 13:28:56 UTC
Parallelism
50
/100
Blocked
44
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,189,142
· 10 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
execOrder
#2
0xab083028
#3
exactInputSingle
#4
transferWithAuthorization
· blocks 4
#9
setData
#5
transferWithAuthorization
· blocks 3
#6
transferWithAuthorization
· blocks 2
#7
transferWithAuthorization
· blocks 1
#8
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
8
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x1f107e2f…749f
0x34b655…2a6f
2 touches
0 conflicts
0x1f459632…a5d9
0x34b655…2a6f
2 touches
0 conflicts
0x3d408431…8444
0x34b655…2a6f
2 touches
0 conflicts
0x3e1d11e9…61de
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)
10 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity