pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,105,573
← previous block
next block →
recent activity
Analyzing
Block #84,105,573
10 transactions · 9 stateful · 2026-06-27 20:37:31 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,105,573
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidityNATIVE
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#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
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x582a46ff…adf9
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0xe91256d2…c2d9
0x5afd3e…7620
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
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
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity