← previous blocknext block →recent activity
Analyzing
Block #73,869,515
14 transactions · 12 stateful · 2026-05-11 10:26:37 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,869,515 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x1414f3…5137
14 touches
21 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1e21f668…9844
0x1414f3…5137
2 touches
0 conflicts
0x860a1df8…ddb9
0x1414f3…5137
2 touches
0 conflicts
0x866b29a7…3b1e
0x1414f3…5137
2 touches
0 conflicts
0xdca6295a…4e9a
0x1414f3…5137
2 touches
0 conflicts
0x03622417…0bd6
0x2880ab…7b43
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)
21 conflicts on slot 0x0000000000…000007
Audit this contract →
← previous block·next block →recent activity