pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,258,202
← previous block
next block →
recent activity
Analyzing
Block #74,258,202
8 transactions · 7 stateful · 2026-05-13 05:35:18 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,258,202
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#5
forward
#4
0x926c56be
· blocks 2
#6
swapExactIn
· blocks 1
#7
swapExactIn
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x16f33ee9…a797
0x699abc…6a3b
4 touches
1 conflict
0x7e59744a…8354
0x699abc…6a3b
4 touches
1 conflict
0xa10d0920…f762
0x065c9d…c394
3 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xf6894ca9…5616
0x065c9d…c394
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:
USDC (USDC)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity