pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,161,698
← previous block
next block →
recent activity
Analyzing
Block #73,161,698
11 transactions · 9 stateful · 2026-05-08 03:40:11 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,161,698
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69fd5b93
#2
0x69fd5b93
#3
0x39435dac
· blocks 2
#4
0x121eab2f
#7
redeemDelegations
#8
0x69fd5b93
#9
0xeffdedb0
#10
setData
#5
0x98717539
· blocks 1
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0xa7a586ac…c700
0x34b655…2a6f
6 touches
3 conflicts
0xdb907629…39aa
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x5728edaf…f1d4
0x34b655…2a6f
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x578e7f66…1b56
0x34b655…2a6f
4 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:
0x34b6552d…112a6f
3 conflicts on slot
0x388e001a16…e57e04
Audit this contract →
← previous block
·
next block →
recent activity