pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,544,660
← previous block
next block →
recent activity
Analyzing
Block #80,544,660
10 transactions · 8 stateful · 2026-06-11 08:38:48 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,544,660
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x05ee6a22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#7
updatePriceFeedsIfNecessary
#8
0xdde17d…e5ac
#9
0xc7e3ec2c
#6
0x42bbae7a
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d360b55…d4f5
0x80f006…d585
4 touches
1 conflict
0x2d360b55…d4f6
0x80f006…d585
4 touches
1 conflict
0xbfe7fd3a…3168
0x3bd359…433a
4 touches
1 conflict
0x68213b65…780d
0xba1333…9ba9
4 touches
1 conflict
0x00000000…0036
0xd0fd2c…6154
4 touches
1 conflict
0xbfda0172…3a17
0xd0fd2c…6154
4 touches
1 conflict
0x00000000…0004
0xdb39a9…613c
4 touches
1 conflict
0xbb371eab…3efc
0xdb39a9…613c
4 touches
1 conflict
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:
0x80f00661…45d585
1 conflict on slot
0x2d360b5596…0bd4f5
Audit this contract →
← previous block
·
next block →
recent activity