pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,630,255
← previous block
next block →
recent activity
Analyzing
Block #80,630,255
11 transactions · 9 stateful · 2026-06-11 18:11:13 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,630,255
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x6c05cd2b
#3
0x5bf9264c
· blocks 1
#5
0x0c7abd22
#6
updateDataFeedsValuesPartial
#7
approve
#8
executeBatch
#9
setData
#10
0x84a0a0…c6a2
#4
0x5bf9264c
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
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x207ff903…0cd2
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0xfbe161dd…757b
0x3bd359…433a
2 touches
0 conflicts
0xf047b0c5…2800
0x425cbb…c36f
2 touches
0 conflicts
0xf047b0c5…2802
0x425cbb…c36f
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity