pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,116,740
← previous block
next block →
recent activity
Analyzing
Block #99,116,740
11 transactions · 11 stateful · 2026-08-25 18:40:37 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,116,740
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
permit2TransferAndMulticall
#3
0x5acec890
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
placeAndExecuteMarketSell
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#10
execOrders
#7
placeAndExecuteMarketSell
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
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x05d7c284…1795
0x065c9d…c394
4 touches
1 conflict
0x1825deaa…f973
0x09475a…400f
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x74f7e0a9…1ab7
0x1c8a33…d316
2 touches
0 conflicts
0x856d36e4…f467
0x5a66a5…cba8
2 touches
0 conflicts
0x02f4f6e2…47c6
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:
USDC (USDC)
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity