pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,453,157
← previous block
next block →
recent activity
Analyzing
Block #84,453,157
12 transactions · 11 stateful · 2026-06-29 11:13:08 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,453,157
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidityNATIVE
· blocks 1
#3
0x0c7abd22
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updatePrices
#7
withdrawETH
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
0x6a4253bb
#11
setData
#2
removeLiquidity
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88ad90f2…8741
0x5afd3e…7620
4 touches
1 conflict
0xbadcc88d…7d64
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x00000000…0001
0x8b0d32…7367
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)
1 conflict on slot
0x88ad90f246…128741
Audit this contract →
← previous block
·
next block →
recent activity