pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,233,285
← previous block
next block →
recent activity
Analyzing
Block #72,233,285
20 transactions · 17 stateful · 2026-05-03 20:32:52 UTC
Parallelism
80
/100
Blocked
35
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,233,285
· 20 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
0xbbb036a8
· blocks 2
#4
0x69f7b16b
#5
execute
#7
execute
#8
updatePrices
· blocks 3
#12
0x69f7b16b
#13
0x69f7b16b
#14
0x98717539
· blocks 1
#15
0x3f5c179b
#16
forward
#17
updateDataFeedsValuesPartial
#18
setData
#3
exactInput
· blocks 1
#9
updatePrices
· blocks 2
#19
0x39435dac
#6
exactInputSingle
#10
updatePrices
· blocks 1
#11
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
8
w0
9
w1
10
w2
11
w3
14
w0
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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:
0x7e9d3a8a…4f9fda
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity