pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,630,678
← previous block
next block →
recent activity
Analyzing
Block #80,630,678
12 transactions · 9 stateful · 2026-06-11 18:14:02 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,630,678
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xdb834625
#2
updatePrices
· blocks 2
#5
0x57368ddf
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#9
0x8e1ed7…6997
#10
0xebe554…fbb4
#11
0xc7e3ec2c
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb18bf8…e9f3
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x00000000…0004
0x69df8a…6292
2 touches
0 conflicts
0x9fe176d4…3669
0x69df8a…6292
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:
0xb18bf8fc…77e9f3
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity