pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,489,646
← previous block
next block →
recent activity
Analyzing
Block #102,489,646
10 transactions · 8 stateful · 2026-09-06 14:13:14 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,489,646
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 1
#3
0x6c05cd2b
#4
transferWithAuthorization
· blocks 2
#7
0x57368ddf
#8
execFwdPositionOpsV2
#9
execOrders
#2
0x6c05cd2b
#5
transferWithAuthorization
· blocks 1
#6
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x3931dd58…c7f4
0x405b63…7777
4 touches
1 conflict
0x00000000…0002
0x023eb9…b2b4
4 touches
1 conflict
0x4747e6a1…2fb8
0x503d19…1d74
4 touches
1 conflict
0x11c3ab2d…cd65
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…0001
0x023eb9…b2b4
4 touches
1 conflict
0x00000000…000c
0x023eb9…b2b4
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)
3 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity