I am trying to send a transaction.
eth.sendTransaction({from: eth.accounts[0], to: eth.accounts[1], value: web3.toWei(5, "ether")})
eth.sendTransaction({from: eth.accounts[0], to: eth.accounts[1], value: web3.toWei(5, "ether")})
INFO [08-25|21:14:21] Submitted transaction
fullhash=0xe1b58ddcb6d8c3f3a8308e0eb275f10c0c3b7bd8807cd24ff6a315a3917ab2a5
recipient=0x939f34bc9253a62927871c889bcf62f398d264a6 INFO
[08-25|21:14:29] Submitted transaction
fullhash=0x33ca6bb00a70de13bd8b1fdec5d0a7995ad09a90e416ac8ab686fc650a324331
recipient=0x939f34bc9253a62927871c889bcf62f398d264a6 INFO
[08-25|21:14:57] Updated mining threads threads=1
INFO [08-25|21:14:57] Transaction pool price threshold updated
price=18000000000 INFO [08-25|21:14:57] Starting mining operation
INFO [08-25|21:14:57] Commit new mining work
number=1 txs=2 uncles=0 elapsed=73.574ms
But when i run
eth.pendingTransactions
i am able to see the list of above sent transactions
SO my question is
When will the transactions be mined?
P.S.- i am running it on my local machine(private blockchain)
Thanks in advance :)
If you are using private blockchain then you can run miner.start() function using the console. After that it will take 5-6 min and miner will be ready to pick your transaction and automatically coinbase account balance will be increased.
Some time if you send very less gas and gasprice with your transaction with your transaction then may be transaction gets stuck. So please send enough gas with your transaction. It will get executed.
You can also send gas and gasprice in your command as below--
eth.sendTransaction({from: eth.coinbase, to: "0x154230ed91d1e711e56b9c0f88b5ba5fd2bghjgf", value: web3.toWei(5, "ether"),gas:21000,gasPrice:web3.toWei(45,"wei")})
Hope this will help
Related
I run a private network of 6 nodes using substrate node-template v3.0.0. During tests, I noticed a difference between "submitted" and "finished" transactions when sending at a constant transaction rate to the blockchain.
I have sent valid transactions (picture) and there is very big difference between "submitted" and "finished" transactions, what does "submitted" and "finished" transactions actually mean ?
Prometheus queries are respectively:
substrate_sub_txpool_submitted_transactions
substrate_sub_txpool_validations_finished
Also there aren't any invalid transactions.
What happens when my transaction gets confirmed and added to the new block?
I learned that if it doesn't get confirmed it will be stuck in the mempool. And I know that the miner who added the new block will be rewarded with currencies and the tx fees that is included to the block. But I was wondering if there is no reward to the transaction owner?
Can anyone give me an answer?
Transaction owner buys the service. Block producers (miners) sell the service.
Transaction owner cannot be paid for the service that they are buying, because it does not make any sense.
I have a chainlink node, and there are transactions that seem to be stuck. How can I fix pending outgoing confirmations?
Most often, you did not fund your chainlink node account with gas. Go to your configration and grab the ACCOUNT_ADDRESS and send ETH to that address.
The second most common is that you're using an outdated version of the chainlink node. Please use 0.9.4 or higher.
For pending Outgoing Confirmations:
You did not fund your chainlink node account with gas.
The ETH chain is clogged up.
Your MIN_OUTGOING_CONFIRMATIONS variable in your .env is too high (it gets set to a default)
If you see pending transactions at your oracle contracts address then it is likely #2. If you don't see any, it's likely #1.
If #1, you can just send some ETH to your node and it should be fine. You can find your node's address ACCOUNT_ADDRESS in the configuration page of your Chainlink GUI.
If #2 you can either:
You can delete the pending transactions from your database and hope everything clears up (This is an OK solution, hopefully smart contracts have a retry parameter for dealing with you data. But if your node stays stuck, then NO one will be able to get data. )
DELETE FROM job_runs WHERE status = 'pending_outgoing_confirmations';
DELETE FROM tx_attempts WHERE confirmed = 'f';
If you need those transactions to go through, you can rebroadcast the transactions with more ETH gas to push them through faster. This is a little trickier to do. The Chainlink nodes have a built in system to push transactions through without you having to do anything, so hopefully they will kick in.
If #3
Set or change your MIN_OUTGOING_CONFIRMATIONS and restart the node.
For Pending Incoming Confirmations:
This is likely due to network congestion or you're working on a network that doesn't have many transactions. An easy fix is to reduce the number of incoming confirmations and restart your node.
In your .env file, add or set the following:
MIN_INCOMING_CONFIRMATIONS=0
Having OTRS queues to run escalations are fine. The thing is, that the tickets stay escalated if the solution time is exceeded.
The thing is sometimes it is a client responsibility to deliver something to close the ticket.
In this case the client gets a response.
How can I reset the escalation time to the time the ticket is replied and the pending is set to a specific date?
So the escalation time will occur e.g. 1 day after the pending date.
Just check https://www.znuny.com/add-ons/znuny4otrs-repository and follow the instructions. After this the package is available the package manager
try the free add-on Znuny4OTRS-EscalationSuspend. Then you can configure states where escalations are suspended. E.g. a state like 'pending customer feedback'
I want to create an ethereum withdrawal system on my site. I know how to send transactions with web3and do other things but I have one problem. If you are trying to send transaction while you already have a processing transaction you will get {'code': -32000, 'message': 'known transaction: (txn hash)'} error. That means that I can't just process transactions without stopping. So how can I do it? Should I make a queue or something like that? I heard I can do it with promises but I don't know how.