pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,524,122
← previous block
next block →
recent activity
Analyzing
Block #82,524,122
11 transactions · 8 stateful · 2026-06-20 12:35:50 UTC
Parallelism
64
/100
Blocked
38
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,524,122
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
setData
#5
updatePriceFeedsIfNecessary
#6
0x6a36899e
#7
transfer
· blocks 3
#8
transfer
· blocks 2
#9
transfer
· blocks 1
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0cfb5d79…7ccb
0xb754ba…508d
2 touches
0 conflicts
0x0cfb5d79…7ccc
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1a
0xb754ba…508d
2 touches
0 conflicts
0x12117fd0…ec1b
0xb754ba…508d
2 touches
0 conflicts
0x1232a81d…88d7
0xb754ba…508d
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)
6 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity