pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,480,769
← previous block
next block →
recent activity
Analyzing
Block #95,480,769
9 transactions · 9 stateful · 2026-08-12 23:51:37 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,480,769
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
placeAndExecuteMarketSell
· blocks 2
#6
0x0f6795d9
#7
transfer
#8
setData
#4
placeAndExecuteMarketBuy
· blocks 1
#5
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0x47a9d778…e89b
0xa6afd3…d132
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x55152f64…ec30
0x34b655…2a6f
2 touches
0 conflicts
0x5692e125…1727
0x34b655…2a6f
2 touches
0 conflicts
0x68297b76…8e24
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)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity