pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,505,497
← previous block
next block →
recent activity
Analyzing
Block #74,505,497
9 transactions · 8 stateful · 2026-05-14 09:01:08 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,505,497
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
requestOutcomes
#3
updateDataFeedsValuesPartial
#4
deposit
· blocks 1
#6
setData
#7
swapExactIn
· blocks 1
#5
transfer
#8
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x545dc77f…e68c
0x699abc…6a3b
4 touches
1 conflict
0xceded178…c087
0x699abc…6a3b
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x04a746ba…cd43
0x0ac7c3…d447
2 touches
0 conflicts
0x0934900c…11b1
0x0ac7c3…d447
2 touches
0 conflicts
0x0fbce525…69a6
0x0ac7c3…d447
2 touches
0 conflicts
0x1658cef1…e6dc
0x0ac7c3…d447
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
0x545dc77f5a…0ae68c
Audit this contract →
← previous block
·
next block →
recent activity