pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,482,705
← previous block
next block →
recent activity
Analyzing
Block #73,482,705
24 transactions · 21 stateful · 2026-05-09 15:16:13 UTC
Parallelism
71
/100
Blocked
43
%
Avg conflicts / tx
1.04
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,482,705
· 24 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x0c7abd22
#2
0xb264ae19
#3
updatePrices
#4
0x39435dac
#5
0x98717539
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updatePosition
#10
forward
#11
0x5339c59f
· blocks 4
#13
0x5339c59f
· blocks 4
#21
0xed82b078
#22
setData
#23
0x39435dac
#6
0x98717539
#12
0x5339c59f
· blocks 3
#15
0x5339c59f
· blocks 3
#14
0x5339c59f
· blocks 2
#16
0x5339c59f
· blocks 2
#17
0xed82b078
· blocks 3
#18
0xed82b078
· blocks 2
#19
0xed82b078
· blocks 1
#20
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
11
w0
12
w1
13
w0
14
w2
15
w1
16
w2
17
w3
18
w4
19
w5
20
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity