pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,380,866
← previous block
next block →
recent activity
Analyzing
Block #80,380,866
10 transactions · 7 stateful · 2026-06-10 14:27:44 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,380,866
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a2974d8
· blocks 1
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x99c0e8…f5cf
#9
swap
#6
0x6a2974d8
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x081393…20b3
2 touches
0 conflicts
0x8ee994de…02b2
0x081393…20b3
2 touches
0 conflicts
0xbb371eab…3efc
0x081393…20b3
2 touches
0 conflicts
0x866bf367…7a60
0x188d58…ea8e
2 touches
0 conflicts
0x866bf367…7a61
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity