pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,429,090
← previous block
next block →
recent activity
Analyzing
Block #72,429,090
25 transactions · 22 stateful · 2026-05-04 18:21:01 UTC
Parallelism
84
/100
Blocked
59
%
Avg conflicts / tx
0.76
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,429,090
· 25 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#4
0x69f8e404
· blocks 1
#5
0x9036287a
· blocks 4
#9
0x16040cc9
#10
0x69f8e404
#11
0x98717539
· blocks 3
#14
updateDataFeedsValuesPartial
#15
updateDataFeedsValuesPartial
#16
0x69f8e405
#17
forward
#18
setData
#2
0x0c7abd22
· blocks 1
#6
0x69f8e405
#7
execute
#8
exactOutputSingle
#12
0x98717539
· blocks 2
#19
0x3f5c179b
· blocks 2
#22
0xed82b078
#3
0x0c7abd22
#13
0x98717539
#20
0xed82b078
· blocks 1
#23
0x39435dac
· blocks 1
#21
0xed82b078
#24
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
5
w0
6
w1
7
w1
8
w1
11
w0
12
w1
13
w2
19
w1
20
w2
21
w3
22
w1
23
w2
24
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0x812b09c7…50b2
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x7322fb4a…635b
0x1b6862…e19c
4 touches
1 conflict
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:
0x065c9d28…a9c394
6 conflicts on slot
0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block
·
next block →
recent activity