pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,021,816
← previous block
next block →
recent activity
Analyzing
Block #95,021,816
11 transactions · 11 stateful · 2026-08-11 09:08:44 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
#95,021,816
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xc9623387
#4
execFwdPositionOps
#5
executeBatch
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a7ae713
#9
setData
#10
execOrders
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x40226d20…1ff7
0x754704…b603
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0x51dd81b2…a171
0x99c7a7…8bf0
4 touches
1 conflict
0xb968c832…9b6a
0x99c7a7…8bf0
4 touches
1 conflict
0x613560f2…8d9e
0x928dc8…8207
2 touches
0 conflicts
0x6ede85f4…0b8a
0x928dc8…8207
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0xe96cbc90aa…eebe66
Audit this contract →
← previous block
·
next block →
recent activity