pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,351,190
← previous block
next block →
recent activity
Analyzing
Block #74,351,190
9 transactions · 9 stateful · 2026-05-13 15:53:44 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,351,190
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x719d975a
· blocks 1
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
updatePriceFeedsIfNecessary
#7
forward
#8
setData
#3
flash
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
0xac5f9d42…6ace
0x3bd359…433a
4 touches
1 conflict
0x4a50a859…1ed9
0x754704…b603
4 touches
1 conflict
0xf047b0c5…2800
0x9b3cc3…0880
4 touches
1 conflict
0xf047b0c5…2803
0x9b3cc3…0880
4 touches
1 conflict
0xf047b0c5…2804
0x9b3cc3…0880
4 touches
1 conflict
0xf6802cf0…344f
0x000000…012a
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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
0xac5f9d4259…5c6ace
Audit this contract →
← previous block
·
next block →
recent activity