pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,749,032
← previous block
next block →
recent activity
Analyzing
Block #73,749,032
11 transactions · 9 stateful · 2026-05-10 20:59:23 UTC
Parallelism
55
/100
Blocked
44
%
Avg conflicts / tx
0.91
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,749,032
· 11 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
updatePrices
· blocks 4
#3
updatePrices
#7
updateDataFeedsValuesPartial
#8
0x0c7abd22
#9
setData
#10
0x39435dac
#2
updatePrices
· blocks 3
#4
updatePrices
· blocks 2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7f81fb82…633e
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
0x065c9d…c394
2 touches
0 conflicts
0xf77ec486…fc03
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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:
0xab35264b…1cfa38
10 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity