pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,506,098
← previous block
next block →
recent activity
Analyzing
Block #74,506,098
10 transactions · 7 stateful · 2026-05-14 09:05:11 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,506,098
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#5
0x6df9e92b
#6
0x6a0590bf
#7
setData
#8
swapExactIn
· blocks 1
#9
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x175aa81c…f6fb
0x699abc…6a3b
4 touches
1 conflict
0x4b3d048d…7f83
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0xf853eb8e…401e
0x34b655…2a6f
2 touches
0 conflicts
0x5593214e…dfc1
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
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:
0x699abc15…c86a3b
1 conflict on slot
0x175aa81c6f…2ff6fb
Audit this contract →
← previous block
·
next block →
recent activity