pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,419,052
← previous block
next block →
recent activity
Analyzing
Block #74,419,052
8 transactions · 7 stateful · 2026-05-13 23:25:27 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,419,052
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
collect
· blocks 1
#6
0x6a0508df
#7
setData
#5
0xec2bd3f2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f1c865b…052a
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x399cd013…b14f
0x23ae8c…7777
2 touches
0 conflicts
0xd352f775…a505
0x39b9e0…7777
2 touches
0 conflicts
0xb4b3c404…f0aa
0x3bd359…433a
2 touches
0 conflicts
0xfcdba3b0…cfc2
0x3bd359…433a
2 touches
0 conflicts
0x8e07e07d…65ff
0x579d00…83f8
2 touches
0 conflicts
0x8e07e07d…6600
0x579d00…83f8
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:
0x3bd359c1…15433a
1 conflict on slot
0x2f1c865b13…49052a
Audit this contract →
← previous block
·
next block →
recent activity