pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,736,366
← previous block
next block →
recent activity
Analyzing
Block #74,736,366
10 transactions · 6 stateful · 2026-05-15 10:46:59 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,736,366
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#4
updatePrices
#5
0x5bf9264c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#9
setData
#2
execute
· blocks 1
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x4aa4f53b…89a1
0x188d58…ea8e
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
6 touches
3 conflicts
0x0ccbaa07…1669
0x754704…b603
2 touches
0 conflicts
0x6a5f931b…aa94
0x754704…b603
2 touches
0 conflicts
0x7fc5284c…6d5c
0x754704…b603
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x754704bc…afb603
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity