pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,337,994
← previous block
next block →
recent activity
Analyzing
Block #73,337,994
10 transactions · 9 stateful · 2026-05-08 23:13:22 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,337,994
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
0x5bf9264c
#4
0x5bf9264c
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
· blocks 1
#8
0xeffdedb0
#9
setData
#7
0x5339c59f
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
0xbd7e37a9…9eb5
0x065c9d…c394
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x33f2d9b1…b689
0x34b655…2a6f
2 touches
0 conflicts
0x403295dc…8fb0
0x34b655…2a6f
2 touches
0 conflicts
0x693d979a…f2bd
0x34b655…2a6f
2 touches
0 conflicts
0x8331fa21…3742
0x34b655…2a6f
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