pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,623,262
← previous block
next block →
recent activity
Analyzing
Block #84,623,262
9 transactions · 7 stateful · 2026-06-30 06:07:42 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
#84,623,262
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
removeLiquidityNATIVE
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x04b127…0063
#7
0xf5c934…f775
#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
0x838e0f29…7f64
0x5afd3e…7620
6 touches
3 conflicts
0x81f46526…4c0d
0x5afd3e…7620
6 touches
3 conflicts
0xebcd072d…7736
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x4de67fca…e8a3
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0001
0x8b0d32…7367
2 touches
0 conflicts
0x00000000…0006
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)
3 conflicts on slot
0x838e0f29c8…227f64
Audit this contract →
← previous block
·
next block →
recent activity