pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,285,331
← previous block
next block →
recent activity
Analyzing
Block #74,285,331
10 transactions · 9 stateful · 2026-05-13 08:35:42 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,285,331
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
· blocks 1
#2
0xed82b078
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
setData
#7
updatePriceFeedsIfNecessary
#8
0xa09e9040
#9
forward
#3
swapWithBackendSignature
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f5c02f…6853
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x850662…52d0
4 touches
1 conflict
0x00000000…0002
0x850662…52d0
4 touches
1 conflict
0x00000000…0004
0x850662…52d0
4 touches
1 conflict
0xb1632c2f…d991
0x0a3323…0a3c
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xf823e97f…2ee6
0x065c9d…c394
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
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:
Wrapped MON (WMON)
1 conflict on slot
0x63f5c02f70…9e6853
Audit this contract →
← previous block
·
next block →
recent activity