pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,229,148
← previous block
next block →
recent activity
Analyzing
Block #94,229,148
9 transactions · 7 stateful · 2026-08-08 14:28:41 UTC
Parallelism
56
/100
Blocked
43
%
Avg conflicts / tx
0.44
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,229,148
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x39435dac
#2
placeAndExecuteMarketSell
· blocks 2
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#3
placeAndExecuteMarketSell
· blocks 1
#4
placeAndExecuteMarketBuy
· blocks 1
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xefeacf2c…990e
0x065c9d…c394
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4bc1b6fd…ce27
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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