pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,654,309
← previous block
next block →
recent activity
Analyzing
Block #82,654,309
12 transactions · 7 stateful · 2026-06-21 03:07:26 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,654,309
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidity
· blocks 1
#3
execOrders
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#2
removeLiquidityNATIVE
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
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0xb98b9e9d…a785
0x3bd359…433a
2 touches
0 conflicts
0x2665ad47…aeb4
0x5afd3e…7620
2 touches
0 conflicts
0x36c21b83…406f
0x5afd3e…7620
2 touches
0 conflicts
0x3cb26bc0…f803
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)
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity