pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,977,770
← previous block
next block →
recent activity
Analyzing
Block #94,977,770
11 transactions · 9 stateful · 2026-08-11 05:27:09 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,977,770
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
redeemDelegations
#6
placeAndExecuteMarketBuy
· blocks 1
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
setData
#7
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb0aa0f6…de63
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x7e0b7922…c351
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x320701d5…f9f4
0x34b655…2a6f
2 touches
0 conflicts
0x46de473e…80da
0x34b655…2a6f
2 touches
0 conflicts
0x4af8f8d2…0850
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xdb0aa0f67c…78de63
Audit this contract →
← previous block
·
next block →
recent activity