pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,745,660
← previous block
next block →
recent activity
Analyzing
Block #80,745,660
11 transactions · 8 stateful · 2026-06-12 07:00:40 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,745,660
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xaf5e395a
· blocks 2
#2
0x719d975a
#3
0x23afbff3
#5
execute
#6
updatePrices
#7
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#4
exactOutputSingle
· blocks 1
#8
0xfc8ff304
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
6 touches
3 conflicts
0x18aed20c…48f3
0x000000…012a
6 touches
3 conflicts
0x00000000…0000
0xd5b70d…615b
6 touches
3 conflicts
0x00000000…0005
0xd5b70d…615b
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x1058984b…de77
0x3bd359…433a
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:
0xd5b70d70…f4615b
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity