pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,630,568
← previous block
next block →
recent activity
Analyzing
Block #80,630,568
11 transactions · 9 stateful · 2026-06-11 18:13:19 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,630,568
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateTemporalNumericValuesV1
#7
0x3f5c179b
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
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
0x04d9a08c…fe81
0xacc0a0…fd62
2 touches
0 conflicts
0x1632adac…6043
0xacc0a0…fd62
2 touches
0 conflicts
0x234fa9a6…ede0
0xacc0a0…fd62
2 touches
0 conflicts
0x5250d39b…c3fb
0xacc0a0…fd62
2 touches
0 conflicts
0x58a1ffb8…36a0
0xacc0a0…fd62
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