pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,421,394
← previous block
next block →
recent activity
Analyzing
Block #93,421,394
13 transactions · 13 stateful · 2026-08-05 18:42:25 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,421,394
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrder
· blocks 1
#4
updatePrices
#5
permit2TransferAndMulticall
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execOrders
#10
0x6a738488
#11
transfer
#12
setData
#2
matchOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2b4ba7…f42d
0x754704…b603
4 touches
1 conflict
0xc07e7b41…7f0a
0x754704…b603
4 touches
1 conflict
0xc084205e…d72d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x3cbf66d3…90fc
0x754704…b603
4 touches
1 conflict
0xdd6cf50f…e383
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:
USDC (USDC)
1 conflict on slot
0x9b2b4ba7eb…e3f42d
Audit this contract →
← previous block
·
next block →
recent activity