pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,136,961
← previous block
next block →
recent activity
Analyzing
Block #85,136,961
9 transactions · 7 stateful · 2026-07-02 15:14:38 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,136,961
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
removeLiquidityNATIVE
· blocks 2
#3
multicall
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#2
removeLiquidity
· blocks 1
#8
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37b32364…c4ab
0x5afd3e…7620
6 touches
3 conflicts
0xe42e4150…c389
0x5afd3e…7620
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0xff68ee4c…37e3
0x1111b3…4111
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x570bc6a6…b037
0x5afd3e…7620
2 touches
0 conflicts
0xa8739397…39e2
0x5afd3e…7620
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:
Liquidity Book Token (LBT)
3 conflicts on slot
0x37b32364d1…b0c4ab
Audit this contract →
← previous block
·
next block →
recent activity