pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,506,034
← previous block
next block →
recent activity
Analyzing
Block #74,506,034
13 transactions · 12 stateful · 2026-05-14 09:04:45 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,506,034
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
approve
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a0590a5
#7
deposit
· blocks 1
#9
setData
#10
approve
#11
approve
#12
0x39435dac
#8
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ff1d43f…d21c
0x3bd359…433a
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x7b43f938…3650
0x000000…012a
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a995
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a997
0x188d58…ea8e
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
0x2ff1d43ff1…81d21c
Audit this contract →
← previous block
·
next block →
recent activity