pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,652,154
← previous block
next block →
recent activity
Analyzing
Block #73,652,154
10 transactions · 8 stateful · 2026-05-10 10:05:38 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,652,154
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
#5
forward
#6
0x5339c59f
· blocks 1
#8
setData
#9
0xcf5e2743
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0e8f48d1…5729
0x065c9d…c394
2 touches
0 conflicts
0xa3a9a22a…14d6
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000d
0x124fe2…6ed9
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
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity