pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,314,510
← previous block
next block →
recent activity
Analyzing
Block #72,314,510
8 transactions · 7 stateful · 2026-05-04 05:37:37 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,314,510
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf99cae99
· blocks 1
#2
exactInputSingle
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x69f83118
#7
setData
#3
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2bdc436…a7ff
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x08012a78…50c2
0x065c9d…c394
2 touches
0 conflicts
0x0984a2da…3fdf
0x065c9d…c394
2 touches
0 conflicts
0x2f5694dc…92b6
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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
0xa2bdc43692…d5a7ff
Audit this contract →
← previous block
·
next block →
recent activity