pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,349,512
← previous block
next block →
recent activity
Analyzing
Block #95,349,512
10 transactions · 10 stateful · 2026-08-12 12:48:56 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,349,512
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
updatePriceFeedsIfNecessary
#5
0x3f5c179b
· blocks 1
#7
transferWithAuthorization
#8
setData
#9
0x59558d29
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x098db796…75a4
0x34b655…2a6f
2 touches
0 conflicts
0x11b46169…0e8b
0x34b655…2a6f
2 touches
0 conflicts
0x1490e80a…c5d3
0x34b655…2a6f
2 touches
0 conflicts
0x15ab76bf…748a
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity