pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,660,699
← previous block
next block →
recent activity
Analyzing
Block #73,660,699
11 transactions · 9 stateful · 2026-05-10 11:03:15 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,660,699
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#3
0x0c7abd22
· blocks 1
#5
0x05ee6a22
#7
0x62be7533
#8
0x6a00666b
#9
setData
#10
0x39435dac
#2
0x1094dc9f
· blocks 1
#6
0x0c7abd22
#4
0x42dd8743
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w2
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8c9dd97b…e1fb
0x065c9d…c394
4 touches
1 conflict
0xe40ed036…1127
0xd32edf…ff58
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xbd45e74e…2216
0x000000…012a
2 touches
0 conflicts
0x91f57f15…a54b
0x065c9d…c394
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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
3 conflicts on slot
0xc9e9752290…9c3519
Audit this contract →
← previous block
·
next block →
recent activity