pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,299,738
← previous block
next block →
recent activity
Analyzing
Block #95,299,738
11 transactions · 10 stateful · 2026-08-12 08:36:49 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,299,738
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
execOrders
· blocks 1
#4
repayWithCollateral
#6
updateDataFeedsValuesPartial
#7
0x6a7c3119
#8
transfer
· blocks 1
#10
setData
#3
execFwdPositionOps
#5
execFwdPositionOps
#9
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9eb6226d…e53f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc44266f9…4b08
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d47
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d48
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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)
1 conflict on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity