pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,576,424
← previous block
next block →
recent activity
Analyzing
Block #72,576,424
9 transactions · 8 stateful · 2026-05-05 10:42:08 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,576,424
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
0x42bbae7a
#4
updatePriceFeedsIfNecessary
#6
0xc5a04723
#7
updateDataFeedsValuesPartial
#8
setData
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x38c281c3…23bc
0x065c9d…c394
2 touches
0 conflicts
0x654f02ad…2bb2
0x065c9d…c394
2 touches
0 conflicts
0x8d0f0a7e…8127
0x065c9d…c394
2 touches
0 conflicts
0x943770dd…3248
0x065c9d…c394
2 touches
0 conflicts
0x960eff19…bbdd
0x065c9d…c394
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity