pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,963,154
← previous block
next block →
recent activity
Analyzing
Block #94,963,154
9 transactions · 7 stateful · 2026-08-11 04:13:39 UTC
Parallelism
56
/100
Blocked
43
%
Avg conflicts / tx
0.56
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,963,154
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 2
#2
0x80419567
#3
updatePrices
#4
updateDataFeedsValuesPartial
#8
setData
#5
placeAndExecuteMarketBuy
· blocks 2
#6
placeAndExecuteMarketBuy
· blocks 1
#7
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xf412e018…1c72
0x065c9d…c394
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
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