pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,498,849
← previous block
next block →
recent activity
Analyzing
Block #84,498,849
13 transactions · 10 stateful · 2026-06-29 16:18:00 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,498,849
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
removeLiquidity
· blocks 1
#3
0x6b8f732b
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
forward
#7
0xed82b078
#8
setData
#9
0x39435dac
#10
0x39435dac
#12
0xc7e3ec2c
#11
0x5d2fd812
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c81d8e4…385f
0x5afd3e…7620
4 touches
1 conflict
0xe3bc19b1…7713
0x5afd3e…7620
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a996
0x188d58…ea8e
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
0x1c81d8e4ba…83385f
Audit this contract →
← previous block
·
next block →
recent activity