pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,538,483
← previous block
next block →
recent activity
Analyzing
Block #74,538,483
12 transactions · 9 stateful · 2026-05-14 12:43:31 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,538,483
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
exactInputSingle
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
#5
0x5339c59f
#6
setData
#7
0x59ffd6…d7bd
#8
0x97313c…3331
#9
swapExactIn
· blocks 1
#11
0x39435dac
#10
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1a28017…3af1
0x699abc…6a3b
4 touches
1 conflict
0x2a92e0ec…124d
0x754704…b603
4 touches
1 conflict
0x8955336a…1fad
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x3f448602…c37b
0x699abc…6a3b
3 touches
1 conflict
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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
0xa1a28017b3…933af1
Audit this contract →
← previous block
·
next block →
recent activity