pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,647,467
← previous block
next block →
recent activity
Analyzing
Block #73,647,467
25 transactions · 21 stateful · 2026-05-10 09:34:07 UTC
Parallelism
80
/100
Blocked
24
%
Avg conflicts / tx
0.6
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,647,467
· 25 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
#2
0x6a005187
#3
execute
#4
execute
#5
updatePrices
#6
0x5bf9264c
#7
0x5bf9264c
#8
0x98717539
#9
0xed82b078
#10
0xed82b078
· blocks 3
#12
updateDataFeedsValuesPartial
#13
updateDataFeedsValuesPartial
#14
0x5339c59f
· blocks 4
#19
0x6a005187
#20
setData
#21
0x39435dac
#22
0x39435dac
#23
0x39435dac
#24
0x39435dac
#11
0xed82b078
· blocks 2
#15
0x5339c59f
· blocks 3
#16
0x5339c59f
· blocks 2
#17
0xed82b078
· blocks 1
#18
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
14
w0
15
w1
16
w2
17
w3
18
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x784d7a94…949e
0x1b6862…e19c
2 touches
0 conflicts
0xc9e97522…3519
0x2a68ba…90c5
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:
0x2a68ba18…8e90c5
10 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity