pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,682,535
← previous block
next block →
recent activity
Analyzing
Block #80,682,535
11 transactions · 9 stateful · 2026-06-11 23:59:42 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,682,535
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
· blocks 3
#6
0x98717539
#7
updatePriceFeedsIfNecessary
#8
setData
#9
0x39435dac
#10
0x39435dac
#3
updatePrices
· blocks 2
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x35a92bbe…e17d
0x34b655…2a6f
2 touches
0 conflicts
0x71435d53…11c8
0x34b655…2a6f
2 touches
0 conflicts
0x8b3263d0…5034
0x34b655…2a6f
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:
0x6fae9933…7ba56d
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity