pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,746,569
← previous block
next block →
recent activity
Analyzing
Block #71,746,569
9 transactions · 7 stateful · 2026-05-01 14:28:32 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,746,569
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
updatePrices
#3
swap
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#7
forward
#8
setData
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1150fcd4…5441
0x065c9d…c394
4 touches
1 conflict
0x21bebe8a…febb
0x065c9d…c394
4 touches
1 conflict
0xf8041dd1…50d4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x92ca7af2…f354
0x065c9d…c394
3 touches
1 conflict
0x46ea0add…f960
0x065c9d…c394
3 touches
1 conflict
0x7d9d1eb4…26de
0x065c9d…c394
3 touches
1 conflict
0xdbeb6e62…b9c9
0x065c9d…c394
3 touches
1 conflict
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
0x1150fcd4f9…b15441
Audit this contract →
← previous block
·
next block →
recent activity