pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,869,322
← previous block
next block →
recent activity
Analyzing
Block #73,869,322
13 transactions · 8 stateful · 2026-05-11 10:25:20 UTC
Parallelism
77
/100
Blocked
25
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,322
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a01af08
#2
mint
· blocks 2
#3
0x6a01af08
#4
0x6a01af08
#5
0x6a01af08
#7
updateDataFeedsValuesPartial
#8
0x000000b2
#9
0x0c7abd22
#11
setData
#12
redeemDelegations
#6
mint
· blocks 1
#10
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1738608b…a758
0x065c9d…c394
2 touches
0 conflicts
0x81501d0b…02c8
0x065c9d…c394
2 touches
0 conflicts
0x91910343…ed21
0x065c9d…c394
2 touches
0 conflicts
0x9ec219b1…b3af
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:
Monad Mogs (MOGS)
3 conflicts on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity