pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,868,999
← previous block
next block →
recent activity
Analyzing
Block #73,868,999
9 transactions · 6 stateful · 2026-05-11 10:23:11 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,868,999
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
mint
· blocks 2
#2
exactInputSingle
#3
0x000000b2
#4
updateDataFeedsValuesPartial
#7
0x6a01ae86
#8
setData
#5
mint
· blocks 1
#6
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
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
0x081c0fa5…f8ca
0x1414f3…5137
2 touches
0 conflicts
0x1bdf7913…4391
0x1414f3…5137
2 touches
0 conflicts
0x38d130c8…d5be
0x1414f3…5137
2 touches
0 conflicts
0x533694df…c522
0x1414f3…5137
2 touches
0 conflicts
0x86b816ca…828a
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