pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,649,014
← previous block
next block →
recent activity
Analyzing
Block #73,649,014
11 transactions · 10 stateful · 2026-05-10 09:44:32 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,649,014
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x121eab2f
· blocks 2
#3
0x9e1844c6
#6
settle
#7
updateDataFeedsValuesPartial
#8
0x6a0053f8
#9
setData
#10
0x39435dac
#4
0xed82b078
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x049fe3c6…645f
0x065c9d…c394
2 touches
0 conflicts
0x14f23ceb…0f3e
0x065c9d…c394
2 touches
0 conflicts
0x2a2f516b…018f
0x065c9d…c394
2 touches
0 conflicts
0x51cb13fc…f1a5
0x065c9d…c394
2 touches
0 conflicts
0x874a45a2…9287
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity