pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,903,374
← previous block
next block →
recent activity
Analyzing
Block #94,903,374
12 transactions · 10 stateful · 2026-08-10 23:12:59 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,903,374
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
placeAndExecuteMarketBuy
· blocks 1
#3
placeAndExecuteMarketBuy
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a7a5b73
#9
setData
#10
execOrders
#11
0x59558d29
#4
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
2 touches
0 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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)
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity