pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,399,640
← previous block
next block →
recent activity
Analyzing
Block #73,399,640
13 transactions · 10 stateful · 2026-05-09 06:03:33 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,399,640
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x39435dac
· blocks 1
#5
0x69fecead
#6
0x98717539
· blocks 1
#8
0x69fecead
#9
0x0c7abd22
#10
0xeffdedb0
#11
setData
#12
exactInputSingle
#7
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20ac0567…c954
0x34b655…2a6f
4 touches
1 conflict
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x9cc607d0…c9c7
0x34b655…2a6f
4 touches
1 conflict
0xeb0915f1…c150
0x34b655…2a6f
4 touches
1 conflict
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
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
1 conflict on slot
0x20ac0567fd…2ac954
Audit this contract →
← previous block
·
next block →
recent activity