pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,399,821
← previous block
next block →
recent activity
Analyzing
Block #72,399,821
23 transactions · 21 stateful · 2026-05-04 15:06:02 UTC
Parallelism
65
/100
Blocked
52
%
Avg conflicts / tx
1.57
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,399,821
· 23 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 7
#9
0xcf7468f4
#10
0x1094dc9f
#11
execute
· blocks 1
#12
updatePrices
#13
postPrice
#14
updateDataFeedsValuesPartial
#15
updateDataFeedsValuesPartial
#17
0x96e62922
#19
setData
#20
0x39435dac
· blocks 2
#2
0x0c7abd22
· blocks 7
#21
0x39435dac
· blocks 1
#3
0x0c7abd22
· blocks 5
#22
0x39435dac
#4
0x0c7abd22
· blocks 4
#5
0x0c7abd22
· blocks 5
#6
0x0c7abd22
· blocks 3
#18
0x3f5c179b
#7
0x0c7abd22
· blocks 1
#16
0x0c7abd22
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
6
w5
7
w6
8
w7
16
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a78015d…6bd8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xed863ec8…90d8
0x1b6862…e19c
8 touches
6 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:
0xd32edf66…9fff58
28 conflicts on slot
0x7a78015db9…3f6bd8
Audit this contract →
← previous block
·
next block →
recent activity