pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,868,994
← previous block
next block →
recent activity
Analyzing
Block #73,868,994
10 transactions · 6 stateful · 2026-05-11 10:23:09 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,868,994
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
mint
#2
0x000000b2
#3
updateDataFeedsValuesPartial
#4
mint
· blocks 2
#7
0x5339c59f
#8
setData
#9
exactInputSingle
#5
mint
· blocks 1
#6
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
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
0x24093133…9fcb
0x065c9d…c394
2 touches
0 conflicts
0x018040c7…8944
0x1414f3…5137
2 touches
0 conflicts
0x15c97f91…996b
0x1414f3…5137
2 touches
0 conflicts
0x1bcc9098…a0b5
0x1414f3…5137
2 touches
0 conflicts
0x7109aea5…a355
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)
3 conflicts on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity