pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,579,784
← previous block
next block →
recent activity
Analyzing
Block #93,579,784
10 transactions · 10 stateful · 2026-08-06 07:58:39 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,579,784
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
#5
execFwdPositionOps
· blocks 1
#7
transfer
#8
setData
#9
0xc7e3ec2c
#2
matchOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0xcf3f3349…b858
0x754704…b603
4 touches
1 conflict
0x1d02b391…1b72
0x34b655…2a6f
4 touches
1 conflict
0xb968c832…9b6a
0x99c7a7…8bf0
4 touches
1 conflict
0x51dd81b2…a171
0x99c7a7…8bf0
4 touches
1 conflict
0x15120760…69ed
0x8f415d…5241
3 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
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