pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,502,178
← previous block
next block →
recent activity
Analyzing
Block #73,502,178
8 transactions · 8 stateful · 2026-05-09 17:25:55 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,502,178
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#6
forward
#7
setData
#2
updatePrices
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x9025f173…750f
0x34b655…2a6f
4 touches
1 conflict
0x8240d70c…7c3b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x468d7241…2809
0x34b655…2a6f
2 touches
0 conflicts
0x4ae4b486…d0ec
0x34b655…2a6f
2 touches
0 conflicts
0x693d979a…f2bd
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:
0x34b6552d…112a6f
1 conflict on slot
0xc56d654866…5050a4
Audit this contract →
← previous block
·
next block →
recent activity