pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,649,655
← previous block
next block →
recent activity
Analyzing
Block #73,649,655
16 transactions · 12 stateful · 2026-05-10 09:48:54 UTC
Parallelism
88
/100
Blocked
8
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,649,655
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#4
execute
#5
exactInputSingle
#6
exactInputSingle
#7
execute
#8
claimRewards
#9
updatePrices
#10
0x5bf9264c
#11
0x5bf9264c
#12
0x98717539
#13
0x100000b2
#14
0x100000b2
#15
setData
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f433588…8076
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a567
0x188d58…ea8e
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:
0xd32edf66…9fff58
1 conflict on slot
0x3f433588dd…0a8076
Audit this contract →
← previous block
·
next block →
recent activity