pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,399,642
← previous block
next block →
recent activity
Analyzing
Block #72,399,642
11 transactions · 9 stateful · 2026-05-04 15:04:50 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,399,642
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#2
updatePrices
#3
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
· blocks 1
#7
0x0c7abd22
#8
0xed82b078
· blocks 1
#10
setData
#4
updatePrices
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w0
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x820c0604…50f8
0x065c9d…c394
4 touches
1 conflict
0xa94e1ae3…81e0
0x065c9d…c394
2 touches
0 conflicts
0xac3b02b8…5881
0x065c9d…c394
2 touches
0 conflicts
0xbb8a814f…af11
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity