Compute Units are a measure of the total computing resources that your application uses on BlockVision. Some query interfaces are lightweight and fast (e.g. eth_blockNumber), while others can be more complex and require more resources(e.g. eth_call). Each method is assigned a certain number of computational units derived from the global average duration of each method.
| | | | |
|---|
| Price | $0/Month | $29/Month | $99/Month | $199/Month |
| Compute Unit | 10,000,000 | 100,000,000 | 600,000,000 | 1,500,000,000 |
| Approx Request | 400,000 | 4,000,000 | 24,000,000 | 60,000,000 |
| Compute Units / Second | 300 | 500 | 1,000 | 2,000 |
| Max App | 5 | 6 | 10 | 20 |
| Development Toolkits | ☑️ | ☑️ | ☑️ | ☑️ |
| Archive Node Service | ☑️ | ☑️ | ☑️ | ☑️ |
| Monitor Service | ☑️ | ☑️ | ☑️ | ☑️ |
| Multi-Chain Support | ☑️ | ☑️ | ☑️ | ☑️ |
| Token API | ☑️ | ☑️ | ☑️ | ☑️ |
| NFT API | ☑️ | ☑️ | ☑️ | ☑️ |
| Account API | - | ☑️ | ☑️ | ☑️ |
| MemPool API | - | ☑️ | ☑️ | ☑️ |
| Trace API | - | ☑️ | ☑️ | ☑️ |
For Free Tier, some APIs like Account APIs support 300 free trials.
For Sui RPC endpoint, each RPC call currently consumes 30 compute unit.
| Membership | Cost | Requests per Month | Rate Limit |
|---|
| Free | $0 per month | 330,000 | 10 requests per second |
| Lite | $29 per month | 3,300,000 | 16 requests per second |
| Basic | $99 per month | 20,000,000 | 33 requests per second |
| Pro | $199 per month | 500,000,000 | 66 requests per second |
| Method | CU |
|---|
| eth_chainId | 1 |
| eth_syncing | 1 |
| eth_protocolVersion | 1 |
| net_listening | 1 |
| eth_gasPrice | 1 |
| eth_uninstallFilter | 10 |
| eth_blockNumber | 10 |
| eth_subscribe | 10 |
| eth_unsubscribe | 10 |
| eth_feeHistory | 10 |
| eth_maxProrityFeePerGas | 10 |
| eth_getTransactionReceipt | 15 |
| eth_getTransactionReceiptsByBlockNumber | 15 |
| eth_getUncleByBlockHashAndIndex | 15 |
| eth_getUncleByBlockNumberAndIndex | 15 |
| eth_getTransactionByBlockHashAndIndex | 15 |
| eth_getTransactionByBlockNumberAndIndex | 15 |
| eth_getUncleCountByBlockNumber | 15 |
| eth_getUncleCountByBlockHash | 15 |
| web3_clientVersion | 15 |
| web3_sha3 | 15 |
| eth_getBlockByNumber | 16 |
| eth_getTransactionByHash | 17 |
| eth_getStorageAt | 17 |
| eth_getBalance | 19 |
| eth_getCode | 19 |
| eth_getBlockTransactionCountByHash | 20 |
| eth_getBlockTransactionCountByNumber | 20 |
| eth_getBlockByHash | 21 |
| eth_getTransactionCount | 26 |
| eth_call | 26 |
| eth_getLogs | 75 |
| eth_estimateGas | 80 |
| eth_sendRawTransaction | 250 |
| eth_getBlockReceipts | 500 |
| Method | CU |
|---|
| Retireve Token Activities | 30 |
| Retireve Token Holders | 30 |
| Retireve Account Token Balance | 50 |
| Retireve Token History Price | 75 |
| Retireve Token Detail | 75 |
| Method | CU |
|---|
| Retrieve a Single Asset | 50 |
| Retrieve Assets | 200 |
| Retrieve a Single Collection | 50 |
| Retrieve Collections | 100 |
| Collection Activity | 150 |
| NFT Activity | 150 |
| Account Activity | 150 |
| Order Listing | 100 |
| Order Offers | 100 |
| Order Asset | 50 |
| Method | CU |
|---|
| NFT Portfolio | 100 |
| FT Portfolio | 100 |
| Defi Portfolio | 100 |
| ETH Transaction | 100 |
| Method | CU |
|---|
| eth_getBundleStat | 100 |
| eth_sendBundle | 250 |
| eth_callBundle | 250 |
| Method | CU |
|---|
| trace_block | 69 |
| trace_transaction | 29 |
| trace_get | 75 |
| trace_call | 75 |
WebSocket subscriptions like eth_subscribe on BlockVision are priced based on bandwidth: the amount of data delivered as part of the subscription.
Each subscription type is priced identically, per byte:
On average, websocket subscriptions event sizes range from a minimum of about 75 bytes to a maximum of about 1000 bytes. Specifically, subscribing to newPendingTransactions costs about 2 compute units per event. The event bvPendingTransactions costs about 20 compute units, while newHeads requires about 25 compute units. But the actual situation may be far from this number.
Rate limit serves to protect users from malicious actors or runaway scripts. Each tier has prioritized rate limit allocations designed for ultimate reliability. CUPS is a measure of the number of compute units used per second when making requests. Since each request is weighted differently, the query frequency is limited based on the total compute units used rather than the number of requests.
For example, if you send one web3_sha3(15 CUs), two eth_blockNumber (16 CUs) requests in the same second, you will have a total of 47 CUPS.
| USER | CPUS |
|---|
| Free | 100 |
| Lite | 500 |
| Basic | 1000 |
| Pro | 2000 |
| Enterprise | Custom |
