pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,407,611
← previous block
next block →
recent activity
Analyzing
Block #80,407,611
12 transactions · 10 stateful · 2026-06-10 17:26:00 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,407,611
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x23afbff3
#3
0x6a299ea0
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5bf9264c
· blocks 1
#8
exactInputSingle
#9
exactInputSingle
#10
setData
#11
0xc7e3ec2c
#7
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x5b155cf8…da5d
0x065c9d…c394
2 touches
0 conflicts
0xee32adcf…c026
0x065c9d…c394
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x24b18e…3301
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:
Perpl
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity