pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,869,469
← previous block
next block →
recent activity
Analyzing
Block #73,869,469
11 transactions · 9 stateful · 2026-05-11 10:26:19 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,869,469
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x000000b2
#3
updateDataFeedsValuesPartial
#4
mint
· blocks 1
#5
mint
#7
0x6a01af43
#8
setData
#9
0x785f5745
#10
0x39435dac
#6
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x295f6d19…2dda
0x1414f3…5137
2 touches
0 conflicts
0x52f5212b…5bf8
0x1414f3…5137
2 touches
0 conflicts
0x55a4cdb2…b0e2
0x1414f3…5137
2 touches
0 conflicts
0x60ac5cee…0d2b
0x1414f3…5137
2 touches
0 conflicts
0x1506f538…3bdd
0x34b655…2a6f
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)
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity