pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,293,647
← previous block
next block →
recent activity
Analyzing
Block #74,293,647
13 transactions · 12 stateful · 2026-05-13 09:31:07 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,293,647
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapExactIn
#2
approve
· blocks 1
#4
0x1ffa3c9b
#5
0x5bf9264c
#6
0x5bf9264c
#7
updatePriceFeedsIfNecessary
#8
forward
#9
forward
#10
updateDataFeedsValuesPartial
#11
setData
#12
0x39435dac
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda126ddd…b188
0x7b2728…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5a5038ba…c777
0x065c9d…c394
2 touches
0 conflicts
0xe4b00f4b…34c0
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x3e1523…94aa
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:
0x7b2728c0…a97777
1 conflict on slot
0xda126ddd67…beb188
Audit this contract →
← previous block
·
next block →
recent activity