pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,250,629
← previous block
next block →
recent activity
Analyzing
Block #80,250,629
19 transactions · 14 stateful · 2026-06-09 23:59:42 UTC
Parallelism
89
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,250,629
· 19 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x98717539
#7
setData
#8
0x3f5c179b
#10
exactInputSingle
#11
0x6a28a965
· blocks 1
#13
0x3ad428…8d4f
#14
0xd024b1…922a
#15
0xb4b512…67eb
#16
0xdce1a1…67ab
#17
0x39435dac
#18
0xc7e3ec2c
#9
0x3f5c179b
#12
0x6a28a965
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x179fe783…6945
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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:
0xa6afd386…b0d132
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity