pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,598,479
← previous block
next block →
recent activity
Analyzing
Block #73,598,479
10 transactions · 8 stateful · 2026-05-10 04:05:49 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,598,479
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
updatePrices
#4
updatePrices
#5
0x39435dac
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x6a000495
#2
0x76368669
· blocks 1
#6
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0x08931765…ef79
0x065c9d…c394
5 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0xf6802cf0…344f
0x000000…012a
2 touches
0 conflicts
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
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
3 conflicts on slot
0xc9e9752290…9c3519
Audit this contract →
← previous block
·
next block →
recent activity