pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,869,002
← previous block
next block →
recent activity
Analyzing
Block #73,869,002
9 transactions · 6 stateful · 2026-05-11 10:23:12 UTC
Parallelism
56
/100
Blocked
50
%
Avg conflicts / tx
0.67
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,002
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x7e7dc2…42c6
#2
0x000000b2
#3
updateDataFeedsValuesPartial
#4
mint
· blocks 3
#8
setData
#5
mint
· blocks 2
#6
mint
· blocks 1
#7
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x2029cee1…2fd0
0x1414f3…5137
2 touches
0 conflicts
0x2a888989…2542
0x1414f3…5137
2 touches
0 conflicts
0x4df856f7…3159
0x1414f3…5137
2 touches
0 conflicts
0x6062a746…6d57
0x1414f3…5137
2 touches
0 conflicts
0x7553254b…a8ce
0x1414f3…5137
2 touches
0 conflicts
0xc8d9c451…502e
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)
6 conflicts on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity