Mainnet
Mainnet JSON-RPC
https://monacoin-mainnet.gateway.tatum.io
Free Monacoin RPC (MONA)
Explore Monacoin, a decentralized cryptocurrency designed for fast payments and grassroots adoption. Discover how it empowers peer-to-peer transactions through an open and community-driven blockchain.
99.9%
1
24/7
FREE
Gateway
Connect to Monacoin
Access reliable, enterprise-grade endpoints that power your dApp with ultra-low latency and 99.9% uptime.
Connect to Monacoin Gateway
Make your first RPC call on Monacoin's Blockchain Gateway.
* Rate limit enabled - perfect for testing and development. For production, we recommend to Upgrade.
Ready for production?
Get 200 requests/second, priority support and advanced blockchain features.
Global Load Balancer
Route to nearest node
Batch RPC Calls
Multiple requests at once
Archive Nodes
Historical blockchain data
Debug & Trace
Advanced debugging
Advanced Analytics
Usage & performance
Bring Your Own RPC
Custom RPC gateways
Get Free API Key
Increase your limit and access all network features in Tatum Development Platform.
Smart Contract Tools on Monacoin
Deploy, create, and interact with smart contracts on Monacoin.
Accessible to Everyone
No signup. No paywalls. Just RPC that works. Great ideas come from everywhere.
Our Mission
With love by Tatum
Method reference
Monacoin methods
Every method the Monacoin gateway accepts, grouped by interface. 31 in total, read live from the node rather than kept by hand.
Mainnet is the live Monacoin network. Every transaction it
accepts is final, and every MONA balance it
reports is real money.
There is no public test network for Monacoin on the gateway, so development happens against Mainnet itself. Reads cost nothing and change nothing, which covers most of what you need before you start signing transactions.
Everything below is served over JSON-RPC. Its endpoint differs per network, and all of them are in the gateway list above.
What sits between you and Monacoin
A node is a machine running Monacoin with a copy of the chain. Your code cannot ask the chain directly, it asks a node. The gateway picks a healthy one for every call, so you point at one URL instead of one machine.
Your application
FREE RPC gateway picks a healthy node
Node Node Node
- One URL, nothing to run or keep patched yourself.
- Calls routed to a node that is up and in sync.
- A failing node is skipped rather than returned to you as an error.
JSON-RPC
31 methods https://monacoin-mainnet.gateway.tatum.io
The default. Every wallet, library and framework speaks it, and it is what you want unless you specifically need something else.
One POST carries a method name, its parameters and an id, and the response comes back on the same connection carrying that same id. Requests are independent, so there is no session to keep alive and nothing to reconnect, which is why it runs unchanged behind a load balancer or inside a serverless function. Send an array instead of a single object and the node works through the whole batch in one round trip.
Where it fits
- Anything your library already does for you. ethers, web3.js, viem and their equivalents all target this.
- Batching reads. One array of twenty calls costs one round trip instead of twenty.
- Stateless and serverless deployments, because nothing has to stay connected between calls.
- Historical queries, by passing a block number where you would otherwise pass latest.
Trade-offs
- It cannot push. Finding out that a block landed means polling for it, or moving to WebSocket.
- Wide log queries get refused. Page through in fixed block windows and merge the results yourself.
- Batch responses may come back in any order. Match them on id, never on position.
Enabled and tested methods
Read live from the endpoint, so this is what it actually serves today rather than what the protocol allows in principle. Anything not on this list returns a method-not-found error.
- createrawtransaction
- Builds an unsigned raw transaction from a set of inputs and outputs.
- decoderawtransaction
- Decodes a serialized transaction into readable JSON.
- decodescript
- Decodes a hex script into its assembly form and any addresses it implies.
- estimatefee
- Estimates the fee per kilobyte for confirmation within a number of blocks.
- estimatesmartfee
- Estimates the fee rate needed for confirmation within a target number of blocks.
- getbestblockhash
- Returns the hash of the current chain tip.
- getblock
- Returns a block by hash, either as a summary or with full transaction detail.
- getblockchaininfo
- Returns chain state: height, difficulty, verification progress and active soft forks.
- getblockcount
- Returns the height of the chain tip.
- getblockhash
- Returns the block hash at a given height.
- getblockheader
- Returns a block header without its transactions.
- getblockstats
- Returns per-block statistics such as fee rates, size and transaction counts.
- getchaintips
- Lists known chain tips, including stale and orphaned branches.
- getdifficulty
- Returns the current proof-of-work difficulty.
- getmempoolancestors
- Lists the unconfirmed ancestors of a transaction in the mempool.
- getmempoolcluster
- Returns the cluster of related transactions a mempool entry belongs to.
- getmempooldescendants
- Lists the unconfirmed descendants of a transaction in the mempool.
- getmempoolentry
- Returns mempool details for one transaction, including fees and dependencies.
- getmempoolfeeratediagram
- Returns the fee-rate distribution of the current mempool.
- getmempoolinfo
- Returns mempool size, memory usage and the minimum relay fee.
- getnetworkinfo
- Returns node version, protocol version and connection details.
- getrawmempool
- Lists the transaction IDs currently sitting in the mempool.
- getrawtransaction
- Returns a transaction, either serialized or decoded.
- gettxout
- Returns an unspent transaction output (UTXO), if it is still unspent.
- gettxoutproof
- Returns a Merkle proof that given transactions are included in a block.
- searchrawtransactions
- Returns transactions involving a given address.
- sendrawtransaction
- Broadcasts a signed, serialized transaction to the network.
- testmempoolaccept
- Checks whether a transaction would be accepted into the mempool, without broadcasting it.
- validateaddress
- Checks whether an address is well formed and returns what is known about it.
- verifymessage
- Verifies a message signed by the private key behind an address.
- verifytxoutproof
- Verifies a Merkle proof and returns the transactions it commits to.
Common JSON-RPC errors
What you are most likely to hit calling this interface, and what to do about it.
- -32700
- Parse error. The request body was not valid JSON. Check that the body is serialised JSON and that Content-Type is application/json.
- -32600
- Invalid request. The JSON parsed, but it is not a well-formed JSON-RPC call. Include jsonrpc, method and id fields. A batch must be a non-empty array.
- -32601
- Method not found. This node does not expose the method you called. Check the spelling and the namespace, and confirm the method is in the list above for this network. Tracing methods in particular are not enabled everywhere.
- -32602
- Invalid params. The method exists but the arguments are wrong. Check argument order and types. Most EVM methods want hex-encoded quantities, and a block parameter such as latest or a hex height.
- -32603
- Internal error. The node failed while handling an otherwise valid request. Retry with backoff. If it persists on one method, it is usually that method rather than the node.
- -32000
- Server error. A catch-all the node uses for execution failures, most often a reverted call or a request over a limit. Read the accompanying message. Execution reverted means your call failed on chain, not in transport. Narrow the block range if you are querying logs.
- HTTP 429
- Rate limited. You have exceeded the free tier request allowance. Back off and retry, batch reads into single calls, or move to a dedicated endpoint for production traffic.
- HTTP 413
- Payload too large. The request body exceeded what the node accepts. Split large batches into smaller ones.
Blockchain Data
Indexed Monacoin Data Insights
Complete on-chain data access, no infrastructure to run yourself. Query wallets, tokens, NFTs, and transaction history with lightning-fast APIs.
Learn more
About Monacoin
What it is, and guides for building on it.
Monacoin is a proof-of-work blockchain optimized for efficient peer-to-peer value transfer and everyday digital payments. Originally launched in Japan, the network emphasizes accessibility and decentralization through the use of the Lyra2RE(v2) mining algorithm, which lowers barriers for individual miners and helps prevent excessive mining centralization. Monacoin features fast block times and low transaction fees, making it well suited for microtransactions and retail use cases. Its UTXO-based architecture and Bitcoin-compatible design ensure reliable security through battle-tested cryptography, while enabling seamless integration with wallets, exchanges, and payment services. With a strong community ecosystem and a focus on practical usability, Monacoin delivers a lightweight, resilient blockchain for open digital commerce.
What's new at Tatum on Monacoin?
Oct 8, 2026 Added
Notifications: Robinhood
Robinhood Chain is now live on Tatum’s Blockchain Notifications, with support for all notification types. Receive onc...
Oct 7, 2026 Added
RPC Gateway: WebSockets for Arbitrum and BSC
Stop polling. Start streaming. Tatum WebSocket subscriptions push blockchain updates to your app over a persistent co...
Sep 25, 2026 Deprecated
Harmony Networks Removal
Tatum is decommissioning its hosted Harmony Mainnet S0, Harmony Testnet S0, and Harmony Devnet S0 RPC services follow...
FAQ
Frequently Asked Questions
Everything you need to know about Monacoin RPC endpoints
Quick Answer: What is Monacoin RPC?
RPC (Remote Procedure Call) is the standard way to interact with the network programmatically - reading on-chain data, submitting transactions, and deploying smart contracts through JSON-RPC calls. The free tier ships 5 requests per minute with no registration required, which covers most learning and testing workflows. Production applications typically move to Tatum Premium for 200 requests per second and enterprise-grade reliability.
What is Monacoin RPC?
RPC (Remote Procedure Call) is the interface that lets developers interact with the network: read on-chain data, submit transactions, and deploy smart contracts programmatically over standard JSON-RPC methods, without running your own node.
How do I connect to Monacoin using these RPC endpoints?
Simply copy the RPC endpoint URL from above and configure it in your Web3 library (ethers.js, web3.js), wallet (MetaMask, Trust Wallet), or development tool (Hardhat, Truffle). The endpoint works immediately with no registration required for the free tier.
What are the rate limits for the free RPC tier?
Free tier RPC endpoints are limited to 5 requests per minute. This is perfect for testing and development. For production applications, we recommend upgrading to Tatum Premium which offers 200 requests per second with no daily limits.
Is Monacoin RPC free forever?
Yes! Our free tier RPC endpoints are free forever with 5 requests per minute. This tier is perfect for learning, testing, and small projects. There are no hidden fees or time limits on the free tier.
What happens if I exceed the free tier rate limit?
If you exceed 5 requests per minute on the free tier, you'll receive an HTTP 429 (Too Many Requests) error. This is a standard rate limiting response. To avoid this, you can upgrade to Tatum Premium which offers 200 requests per second with no daily limits, perfect for production applications.
Can I use these Monacoin RPC endpoints with MetaMask?
Yes! You can configure MetaMask to use our RPC endpoints. Simply copy the endpoint URL from above, go to MetaMask Settings > Networks > Add Network (or edit existing), and paste the RPC URL. This works with all EVM-compatible networks, including this one.
Are these RPC endpoints secure?
Yes, all our RPC endpoints use HTTPS encryption and follow enterprise-grade security practices. They're powered by Tatum's infrastructure which maintains 99.9% uptime.
What's the difference between mainnet and testnet RPC endpoints?
Mainnet carries real transactions with real value, so every write is final. Testnet runs on a separate network funded with free test tokens, which makes it the safe place to try new code, retry failed calls, and simulate edge cases. Always validate on testnet before pointing production traffic at mainnet.
How do I troubleshoot RPC connection errors?
If you're experiencing connection errors, check: 1) The RPC endpoint URL is correct, 2) You're not exceeding rate limits (5 req/min for free tier), 3) Your network allows HTTPS connections, 4) The network is currently operational. For persistent issues, check our status page or contact support.
Can I use these endpoints in production?
Free tier endpoints can be used in production for low-traffic applications (under 5 req/min). For production apps with higher traffic, we strongly recommend Tatum Premium for guaranteed uptime, faster rate limits, and enterprise SLA.
Related Blockchains
Explore Other Blockchains
Discover RPC endpoints for other popular blockchain networks
