pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,033,992
← previous block
next block →
recent activity
Analyzing
Block #73,033,992
11 transactions · 8 stateful · 2026-05-07 13:30:46 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,033,992
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
0x98717539
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#3
updatePrices
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x5dc14a96…6816
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c6
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:
0x34b6552d…112a6f
1 conflict on slot
0x388e001a16…e57e04
Audit this contract →
← previous block
·
next block →
recent activity