pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,328,749
← previous block
next block →
recent activity
Analyzing
Block #80,328,749
19 transactions · 12 stateful · 2026-06-10 08:40:31 UTC
Parallelism
79
/100
Blocked
42
%
Avg conflicts / tx
0.47
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,328,749
· 19 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0x5bf9264c
#5
0x5bf9264c
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
0x0f6795d9
#10
0x57368ddf
#11
execute
· blocks 3
#15
0x6a292377
#16
setData
#17
0x831d30…475c
#18
0x5620c6…3955
#2
0x0c7abd22
· blocks 1
#12
execute
· blocks 2
#3
0x0c7abd22
#13
execute
· blocks 1
#14
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
11
w0
12
w1
13
w2
14
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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:
0x24b18eb6…733301
6 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity