pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,276,569
← previous block
next block →
recent activity
Analyzing
Block #80,276,569
10 transactions · 7 stateful · 2026-06-10 02:52:39 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,276,569
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
approve
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x3f5c179b
#8
exactInputSingle
#9
setData
#2
deposit
· blocks 1
#3
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2f00bd34…46a8
0x065c9d…c394
2 touches
0 conflicts
0x59c91d34…c8b1
0x065c9d…c394
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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
0x487d2922ff…7828b6
Audit this contract →
← previous block
·
next block →
recent activity