pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,613,146
← previous block
next block →
recent activity
Analyzing
Block #74,613,146
10 transactions · 9 stateful · 2026-05-14 21:04:57 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,613,146
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a063971
#2
0x1ffa3c9b
· blocks 2
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
addLiquidityNATIVE
#8
0x6a063970
#9
setData
#6
0xed82b078
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x4a4333d9…7eea
0x065c9d…c394
2 touches
0 conflicts
0xced07c71…46ad
0x065c9d…c394
2 touches
0 conflicts
0xf5ec948b…69c6
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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:
0x065c9d28…a9c394
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity