pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,426,905
← previous block
next block →
recent activity
Analyzing
Block #95,426,905
18 transactions · 17 stateful · 2026-08-12 19:20:40 UTC
Parallelism
83
/100
Blocked
12
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,426,905
· 18 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
#3
execOrder
#4
execOrders
#5
0x5acec890
#6
execOrders
#7
updatePrices
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
placeAndExecuteMarketBuy
#11
updatePosition
#12
updateDataFeedsValuesPartial
#13
transfer
· blocks 2
#16
setData
#17
0x59558d29
#14
transfer
· blocks 1
#15
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
13
w0
14
w1
15
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity