pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,330,438
← previous block
next block →
recent activity
Analyzing
Block #80,330,438
10 transactions · 7 stateful · 2026-06-10 08:51:46 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,330,438
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
0x42bbae7a
#5
transfer
#6
setData
#7
0x8f656e…4b56
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678a8de3…7da5
0x34b655…2a6f
4 touches
1 conflict
0x537e2e5b…c3ab
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf737decd…2fdf
0x34b655…2a6f
4 touches
1 conflict
0x1062ca99…dc10
0x34b655…2a6f
2 touches
0 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
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
0x678a8de356…df7da5
Audit this contract →
← previous block
·
next block →
recent activity