pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,215,392
← previous block
next block →
recent activity
Analyzing
Block #95,215,392
9 transactions · 8 stateful · 2026-08-12 01:23:13 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,215,392
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketSell
· blocks 1
#6
0x6a7bcb79
#7
transfer
#8
setData
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x3b56f79b…310f
0x34b655…2a6f
2 touches
0 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
2 touches
0 conflicts
0x4984f7be…d515
0x34b655…2a6f
2 touches
0 conflicts
0x785c87ba…a0f1
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:
Coinbase Wrapped BTC (cbBTC)
1 conflict on slot
0x2b54cadb82…7c4425
Audit this contract →
← previous block
·
next block →
recent activity