pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,228,455
← previous block
next block →
recent activity
Analyzing
Block #72,228,455
9 transactions · 8 stateful · 2026-05-03 20:00:21 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,228,455
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x9036287a
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
setData
#8
updatePosition
#2
updatePrices
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2f51ecdb…8ee2
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x18371df7…12e9
0x065c9d…c394
3 touches
1 conflict
0x4d7e34c2…5549
0x065c9d…c394
3 touches
1 conflict
0x453f38cd…21e0
0x065c9d…c394
2 touches
0 conflicts
0x57e83a30…77bc
0x065c9d…c394
2 touches
0 conflicts
0xe8794253…4ad1
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