pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,233,814
← previous block
next block →
recent activity
Analyzing
Block #102,233,814
9 transactions · 8 stateful · 2026-09-05 16:36:56 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,233,814
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x59558d29
#2
transferWithAuthorization
· blocks 3
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
transfer
#3
transferWithAuthorization
· blocks 2
#4
transferWithAuthorization
· blocks 1
#5
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x12c0e79a…4a1f
0x34b655…2a6f
2 touches
0 conflicts
0x16fc2b4f…7b04
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
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)
6 conflicts on slot
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity