pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,358,586
← previous block
next block →
recent activity
Analyzing
Block #92,358,586
11 transactions · 11 stateful · 2026-08-02 01:34:22 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,358,586
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
placeAndExecuteMarketBuy
· blocks 1
#7
forward
#8
forward
#9
setData
#10
0x59558d29
#2
0x5acec890
#6
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x06b413db…a355
0x34b655…2a6f
2 touches
0 conflicts
0x2e4162fb…bfc1
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0x68a2902c…b23f
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity