pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,653,473
← previous block
next block →
recent activity
Analyzing
Block #73,653,473
12 transactions · 10 stateful · 2026-05-10 10:14:32 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,653,473
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
exactOutputSingle
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x5339c59f
· blocks 2
#9
0x6a005b00
#10
setData
#11
jMMeC
#7
0x5339c59f
· blocks 1
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b10a7d5…82c1
0x065c9d…c394
2 touches
0 conflicts
0x30ac5756…a6eb
0x065c9d…c394
2 touches
0 conflicts
0x529acb6a…fcc6
0x065c9d…c394
2 touches
0 conflicts
0x769c968e…ba71
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
3 conflicts on slot
0x7f81fb82c1…ec633e
Audit this contract →
← previous block
·
next block →
recent activity