pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,744,631
← previous block
next block →
recent activity
Analyzing
Block #89,744,631
10 transactions · 10 stateful · 2026-07-23 21:59:35 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,744,631
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
execFwdPositionOps
#3
0xce1e7030
· blocks 1
#5
approve
#6
setData
#7
execOrders
#8
execOrders
#9
execOrders
#4
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x449423ba…1e0d
0xe7a4f9…4b2d
4 touches
1 conflict
0x6882c020…1910
0x81a224…7777
4 touches
1 conflict
0x6647c3d1…3d69
0x065c9d…c394
4 touches
1 conflict
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x8f34a624…dd83
0x2a68ba…90c5
4 touches
1 conflict
0x4c770fe0…b972
0x3bd359…433a
4 touches
1 conflict
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
0xddc22bc2be…bf7f7a
Audit this contract →
← previous block
·
next block →
recent activity