pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,684,589
← previous block
next block →
recent activity
Analyzing
Block #80,684,589
13 transactions · 5 stateful · 2026-06-12 00:13:23 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,684,589
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x3f5c179b
#9
0x3b48b5…704b
#10
0x38e4f1…6630
#11
transfer
#12
setData
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
2 touches
0 conflicts
0x0317aa85…22e4
0x7d37a9…7126
2 touches
0 conflicts
0x51e6ea94…98b1
0x7d37a9…7126
2 touches
0 conflicts
0x00000000…003d
0x851145…3f07
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity