pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,035,128
← previous block
next block →
recent activity
Analyzing
Block #73,035,128
17 transactions · 10 stateful · 2026-05-07 13:38:19 UTC
Parallelism
88
/100
Blocked
10
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,035,128
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa19a5a12
· blocks 1
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
0x5bf9264c
#7
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
0x0c7abd22
#10
0x62be7533
#11
forward
#12
0x39435dac
#13
0x05fc3bd7
#14
0xeffdedb0
#15
setData
#16
0x01020400
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
16
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa5815d74…9a7d
0x065c9d…c394
2 touches
0 conflicts
0xfbad2c6c…0d32
0x188d58…ea8e
2 touches
0 conflicts
0xfbad2c6c…0d33
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
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:
0x754704bc…afb603
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity