pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,170,041
← previous block
next block →
recent activity
Analyzing
Block #94,170,041
10 transactions · 8 stateful · 2026-08-08 09:29:08 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,170,041
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
placeAndExecuteMarketBuy
· blocks 1
#3
0xd62522e3
#4
verifyOracleProofV2
#5
execFwdPositionOps
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xc7e3ec2c
#2
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4265ca54…c8d0
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x72a152dd…9daa
0x16f70c…c3dd
2 touches
0 conflicts
0x2d295d92…0bff
0x754704…b603
2 touches
0 conflicts
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0x595233b5…c4aa
0x754704…b603
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
0x4265ca5447…77c8d0
Audit this contract →
← previous block
·
next block →
recent activity