← previous blocknext block →recent activity
Analyzing
Block #73,869,350
17 transactions · 12 stateful · 2026-05-11 10:25:31 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,869,350 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w19w210w311w112w213w314w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x7f81fb82…633e
0x065c9d…c394
4 touches
1 conflict
0xb4f46d38…a9c8
0x065c9d…c394
4 touches
1 conflict
0xa56e58ca…36e5
0x065c9d…c394
4 touches
1 conflict
0x27aceec2…e0bd
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5cc092e3…6128
0x065c9d…c394
4 touches
1 conflict
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