pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,597,942
← previous block
next block →
recent activity
Analyzing
Block #84,597,942
13 transactions · 12 stateful · 2026-06-30 03:19:07 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,597,942
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
forward
#3
addLiquidity
· blocks 1
#5
0x0f6795d9
#6
0x39435dac
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a433623
#10
setData
#11
0x39435dac
#12
0x39435dac
#4
removeLiquidityNATIVE
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4039b31f…0f4a
0x754704…b603
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x1c81d8e4…385f
0x5afd3e…7620
2 touches
0 conflicts
0x63091d17…493d
0x5afd3e…7620
2 touches
0 conflicts
0xaf14377f…d149
0x5afd3e…7620
2 touches
0 conflicts
0xe3bc19b1…7713
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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:
USDC (USDC)
1 conflict on slot
0x4039b31fcf…cb0f4a
Audit this contract →
← previous block
·
next block →
recent activity