pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,469,909
← previous block
next block →
recent activity
Analyzing
Block #93,469,909
12 transactions · 11 stateful · 2026-08-05 22:46:19 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,469,909
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
matchOrders
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
permit2TransferAndMulticall
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
placeAndExecuteMarketBuy
· blocks 1
#11
setData
#10
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xefc4f0f7…a93f
0x065c9d…c394
4 touches
1 conflict
0x7e0b7922…c351
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xca9ad744…4629
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x06e40499…165e
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)
1 conflict on slot
0xa2478c8415…006956
Audit this contract →
← previous block
·
next block →
recent activity