pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,869,392
← previous block
next block →
recent activity
Analyzing
Block #73,869,392
11 transactions · 8 stateful · 2026-05-11 10:25:48 UTC
Parallelism
73
/100
Blocked
25
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,392
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
mint
· blocks 2
#3
0x40e79b1b
#4
0x39435dac
#6
0x000000b2
#7
updateDataFeedsValuesPartial
#9
0x6a01af24
#10
setData
#5
mint
· blocks 1
#8
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
8
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
0x371b98b9…d1c2
0x065c9d…c394
2 touches
0 conflicts
0x7f5ded20…9946
0x065c9d…c394
2 touches
0 conflicts
0x8eaef0e5…1653
0x065c9d…c394
2 touches
0 conflicts
0xb0fd2434…2bc9
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