pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,406,586
← previous block
next block →
recent activity
Analyzing
Block #89,406,586
11 transactions · 10 stateful · 2026-07-22 10:44:03 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,406,586
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0xab083028
#3
0x6a609f6b
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
setData
#8
approve
#9
execOrders
#10
0xc7e3ec2c
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x405da62e…192a
0xa6afd3…d132
4 touches
1 conflict
0xb476ee35…c627
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x12cf6ffc…5f1d
0xa6afd3…d132
3 touches
1 conflict
0x1d8586b7…144a
0xa6afd3…d132
3 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x405da62ebf…42192a
Audit this contract →
← previous block
·
next block →
recent activity