pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,869,453
← previous block
next block →
recent activity
Analyzing
Block #73,869,453
11 transactions · 8 stateful · 2026-05-11 10:26:12 UTC
Parallelism
55
/100
Blocked
50
%
Avg conflicts / tx
0.91
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,453
· 11 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xa09e9040
#2
0x000000b2
#3
mint
· blocks 4
#5
updateDataFeedsValuesPartial
#8
0x85367786
#9
setData
#4
redeemDelegations
· blocks 3
#6
mint
· blocks 2
#7
mint
· blocks 1
#10
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
7
w3
10
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
10 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x210c3be2…b3f2
0x1414f3…5137
2 touches
0 conflicts
0x307a3e5c…c62a
0x1414f3…5137
2 touches
0 conflicts
0x39af9264…9f48
0x1414f3…5137
2 touches
0 conflicts
0x3f04df4d…8916
0x1414f3…5137
2 touches
0 conflicts
0x67c0fd18…cb92
0x1414f3…5137
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)
10 conflicts on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity