Ecoer Logo
VOTING POWER100.00%
DOWNVOTE POWER100.00%
RESOURCE CREDITS100.00%
REPUTATION PROGRESS46.72%
Net Worth
1.614USD
STEEM
1.972STEEM
SBD
1.791SBD
Own SP
11.537SP

Detailed Balance

STEEM
balance
0.001STEEM
market_balance
0.000STEEM
savings_balance
0.000STEEM
reward_steem_balance
1.971STEEM
STEEM POWER
Own SP
11.537SP
Delegated Out
0.000SP
Delegation In
0.000SP
Effective Power
11.537SP
Reward SP (pending)
1.971SP
SBD
sbd_balance
1.791SBD
sbd_conversions
0.000SBD
sbd_market_balance
0.000SBD
savings_sbd_balance
0.000SBD
reward_sbd_balance
0.000SBD
{
  "balance": "0.001 STEEM",
  "savings_balance": "0.000 STEEM",
  "reward_steem_balance": "1.971 STEEM",
  "vesting_shares": "18786.664534 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "sbd_balance": "1.791 SBD",
  "savings_sbd_balance": "0.000 SBD",
  "reward_sbd_balance": "0.000 SBD",
  "conversions": []
}

Account Info

nameusername
id29732
rank113,691
reputation145552329995
created2016-07-22T21:25:57
recovery_accountsteem
proxyNone
post_count46
comment_count0
lifetime_vote_count0
witnesses_voted_for0
last_post2023-05-01T06:29:15
last_root_post2023-05-01T06:29:15
last_vote_time2023-05-01T06:30:33
proxied_vsf_votes0, 0, 0, 0
can_vote1
voting_power9,889
delayed_votes0
balance0.001 STEEM
savings_balance0.000 STEEM
sbd_balance1.791 SBD
savings_sbd_balance0.000 SBD
vesting_shares18786.664534 VESTS
delegated_vesting_shares0.000000 VESTS
received_vesting_shares0.000000 VESTS
reward_vesting_balance3483.413580 VESTS
vesting_balance0.000 STEEM
vesting_withdraw_rate0.000000 VESTS
next_vesting_withdrawal1969-12-31T23:59:59
withdrawn8748657067
to_withdraw8748657067
withdraw_routes0
savings_withdraw_requests0
last_account_recovery1970-01-01T00:00:00
reset_accountnull
last_owner_update1970-01-01T00:00:00
last_account_update1970-01-01T00:00:00
minedNo
sbd_seconds0
sbd_last_interest_payment2021-09-26T18:29:12
savings_sbd_last_interest_payment1970-01-01T00:00:00
{
  "id": 29732,
  "name": "username",
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7xYJJhtUon7SPZV195rnCt8UsCCzh8g5K9PDsrU2kLMBKCQ4Jo",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5MDv7gmhHA1K9W7DQdfx9jtZZGmhT5c1SKqDXaMod8Z32REXPM",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6GZczjf8yYR5ST8Sy2vopEu34J5YgJyLxMSCMLAXKc9juXXi3M",
        1
      ]
    ]
  },
  "memo_key": "STM7x4Q2rZdkC7QZNiKdGcLnvZFMkFSSRmJtrCr7WyfjmLpGYQiPt",
  "json_metadata": "",
  "posting_json_metadata": "",
  "proxy": "",
  "last_owner_update": "1970-01-01T00:00:00",
  "last_account_update": "1970-01-01T00:00:00",
  "created": "2016-07-22T21:25:57",
  "mined": false,
  "recovery_account": "steem",
  "last_account_recovery": "1970-01-01T00:00:00",
  "reset_account": "null",
  "comment_count": 0,
  "lifetime_vote_count": 0,
  "post_count": 46,
  "can_vote": true,
  "voting_manabar": {
    "current_mana": "18584529105",
    "last_update_time": 1682922765
  },
  "downvote_manabar": {
    "current_mana": "4696666132",
    "last_update_time": 1682922765
  },
  "voting_power": 9889,
  "balance": "0.001 STEEM",
  "savings_balance": "0.000 STEEM",
  "sbd_balance": "1.791 SBD",
  "sbd_seconds": "0",
  "sbd_seconds_last_update": "2021-09-26T18:29:12",
  "sbd_last_interest_payment": "2021-09-26T18:29:12",
  "savings_sbd_balance": "0.000 SBD",
  "savings_sbd_seconds": "0",
  "savings_sbd_seconds_last_update": "1970-01-01T00:00:00",
  "savings_sbd_last_interest_payment": "1970-01-01T00:00:00",
  "savings_withdraw_requests": 0,
  "reward_sbd_balance": "0.000 SBD",
  "reward_steem_balance": "1.971 STEEM",
  "reward_vesting_balance": "3483.413580 VESTS",
  "reward_vesting_steem": "1.971 STEEM",
  "vesting_shares": "18786.664534 VESTS",
  "delegated_vesting_shares": "0.000000 VESTS",
  "received_vesting_shares": "0.000000 VESTS",
  "vesting_withdraw_rate": "0.000000 VESTS",
  "next_vesting_withdrawal": "1969-12-31T23:59:59",
  "withdrawn": "8748657067",
  "to_withdraw": "8748657067",
  "withdraw_routes": 0,
  "curation_rewards": 0,
  "posting_rewards": 4436,
  "proxied_vsf_votes": [
    0,
    0,
    0,
    0
  ],
  "witnesses_voted_for": 0,
  "last_post": "2023-05-01T06:29:15",
  "last_root_post": "2023-05-01T06:29:15",
  "last_vote_time": "2023-05-01T06:30:33",
  "post_bandwidth": 0,
  "pending_claimed_accounts": 0,
  "vesting_balance": "0.000 STEEM",
  "reputation": "145552329995",
  "transfer_history": [],
  "market_history": [],
  "post_history": [],
  "vote_history": [],
  "other_history": [],
  "witness_votes": [],
  "tags_usage": [],
  "guest_bloggers": [],
  "rank": 113691
}

Withdraw Routes

IncomingOutgoing
Empty
Empty
{
  "incoming": [],
  "outgoing": []
}
From Date
To Date
usernamereceived 1.971 STEEM, 2.139 SP author reward for @username / the-lightning-network-faq
2023/05/08 06:29:15
authorusername
permlinkthe-lightning-network-faq
sbd payout0.000 SBD
steem payout1.971 STEEM
vesting payout3483.413580 VESTS
Transaction InfoBlock #74433080/Virtual Operation #6
View Raw JSON Data
{
  "trx_id": "0000000000000000000000000000000000000000",
  "block": 74433080,
  "trx_in_block": 4294967295,
  "op_in_trx": 0,
  "virtual_op": 6,
  "timestamp": "2023-05-08T06:29:15",
  "op": [
    "author_reward",
    {
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "sbd_payout": "0.000 SBD",
      "steem_payout": "1.971 STEEM",
      "vesting_payout": "3483.413580 VESTS"
    }
  ]
}
alexmove.witnesssent 0.001 STEEM to @username- "Please support me @alexmove.witness as witness on site https://steemitwallet.com/~witnesses. I send daily Witness vote STEEM reward and developing a learning project SelfDevelopment Club. Your vote is..."
2023/05/01 06:50:03
fromalexmove.witness
tousername
amount0.001 STEEM
memoPlease support me @alexmove.witness as witness on site https://steemitwallet.com/~witnesses. I send daily Witness vote STEEM reward and developing a learning project SelfDevelopment Club. Your vote is very important to me, username! Good luck! 20230501
Transaction InfoBlock #74232820/Trx aec01e4935a705f357a0739b3430a5ed9100ffae
View Raw JSON Data
{
  "trx_id": "aec01e4935a705f357a0739b3430a5ed9100ffae",
  "block": 74232820,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:50:03",
  "op": [
    "transfer",
    {
      "from": "alexmove.witness",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "Please support me @alexmove.witness as witness on site https://steemitwallet.com/~witnesses. I send daily Witness vote STEEM reward and developing a learning project SelfDevelopment Club. Your vote is very important to me, username! Good luck! 20230501"
    }
  ]
}
2023/05/01 06:33:15
voterpixelfan
authorusername
permlinkthe-lightning-network-faq
weight10000 (100.00%)
Transaction InfoBlock #74232484/Trx f45dc5cf304debed89e049b8f84399e5e624d5c4
View Raw JSON Data
{
  "trx_id": "f45dc5cf304debed89e049b8f84399e5e624d5c4",
  "block": 74232484,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:33:15",
  "op": [
    "vote",
    {
      "voter": "pixelfan",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "weight": 10000
    }
  ]
}
2023/05/01 06:33:15
votersteem-holder
authorusername
permlinkthe-lightning-network-faq
weight10000 (100.00%)
Transaction InfoBlock #74232484/Trx ab49b31b92f168c9c6d401fe50333ef1215cfed8
View Raw JSON Data
{
  "trx_id": "ab49b31b92f168c9c6d401fe50333ef1215cfed8",
  "block": 74232484,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:33:15",
  "op": [
    "vote",
    {
      "voter": "steem-holder",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "weight": 10000
    }
  ]
}
usernamepowered up 4.821 STEEM to @username
2023/05/01 06:32:45
fromusername
tousername
amount4.821 STEEM
Transaction InfoBlock #74232474/Trx ec45fef0bdb7bc9562e6f461e16d1a9f5bf57790
View Raw JSON Data
{
  "trx_id": "ec45fef0bdb7bc9562e6f461e16d1a9f5bf57790",
  "block": 74232474,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:32:45",
  "op": [
    "transfer_to_vesting",
    {
      "from": "username",
      "to": "username",
      "amount": "4.821 STEEM"
    }
  ]
}
2023/05/01 06:32:15
voterharkar
authorusername
permlinkthe-lightning-network-faq
weight10000 (100.00%)
Transaction InfoBlock #74232464/Trx a708e2a51514bfa49607991fe5624254079b4a93
View Raw JSON Data
{
  "trx_id": "a708e2a51514bfa49607991fe5624254079b4a93",
  "block": 74232464,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:32:15",
  "op": [
    "vote",
    {
      "voter": "harkar",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "weight": 10000
    }
  ]
}
2023/05/01 06:32:12
voterxpilar
authorusername
permlinkthe-lightning-network-faq
weight10000 (100.00%)
Transaction InfoBlock #74232463/Trx 7eef98404b5f71f43fc4425d9cb070ad452dcdaa
View Raw JSON Data
{
  "trx_id": "7eef98404b5f71f43fc4425d9cb070ad452dcdaa",
  "block": 74232463,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:32:12",
  "op": [
    "vote",
    {
      "voter": "xpilar",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "weight": 10000
    }
  ]
}
2023/05/01 06:31:21
voterusername
authorusername
permlinkre-jl777-re-berniesanders-re-jl777-why-whales-are-needed-and-a-proposal-to-insure-the-massive-success-of-steemit-20160723t175544357z
weight10000 (100.00%)
Transaction InfoBlock #74232447/Trx e696fd1df2a544833462071bf6352fad25ea58ff
View Raw JSON Data
{
  "trx_id": "e696fd1df2a544833462071bf6352fad25ea58ff",
  "block": 74232447,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:31:21",
  "op": [
    "vote",
    {
      "voter": "username",
      "author": "username",
      "permlink": "re-jl777-re-berniesanders-re-jl777-why-whales-are-needed-and-a-proposal-to-insure-the-massive-success-of-steemit-20160723t175544357z",
      "weight": 10000
    }
  ]
}
executive-boardsent 0.001 STEEM to @username- "❗ Hello username, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, jus..."
2023/05/01 06:31:12
fromexecutive-board
tousername
amount0.001 STEEM
memo❗ Hello username, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board.
Transaction InfoBlock #74232444/Trx 37b84b0906c579bde97fdc902c4c974410d6e017
View Raw JSON Data
{
  "trx_id": "37b84b0906c579bde97fdc902c4c974410d6e017",
  "block": 74232444,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:31:12",
  "op": [
    "transfer",
    {
      "from": "executive-board",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "❗ Hello username, great that you are using the STEEM blockchain. The Executive Board is publishing insider infos at https://discord.gg/KyBbmhh on how you will be earning the most coins. It's easy, just follow the instructions. THE 1000X BOOSTER KEY is already waiting for you over there too. 😉 Warm regards, The Executive Board."
    }
  ]
}
2023/05/01 06:30:33
voterusername
authorusername
permlinkthe-lightning-network-faq
weight10000 (100.00%)
Transaction InfoBlock #74232431/Trx 3c94c76745dbf979e7ea24afa974b706ced8bfe5
View Raw JSON Data
{
  "trx_id": "3c94c76745dbf979e7ea24afa974b706ced8bfe5",
  "block": 74232431,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:30:33",
  "op": [
    "vote",
    {
      "voter": "username",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "weight": 10000
    }
  ]
}
usernamepublished a new post: the-lightning-network-faq
2023/05/01 06:29:15
parent author
parent permlinkhive-179944
authorusername
permlinkthe-lightning-network-faq
titleThe Lightning Network FAQ
bodyThis thread is now self-moderated. The previous one got derailed. Please, don't discuss here whether or not the Lightning Network is a good scaling solution. If you don't know anything about the Lightning Network, consider reading "Basics of The Lightning Network" first. Table of contents 1. Lightning basics 2. Wallets 3. Running a node 4. Concerns 5. Other questions Lightning basics How are coins on the Lightning Network different from the on-chain ones? They are exactly the same coins. They are stored in a multi-signature address and transactions are settled between two parties without broadcasting anything to the blockchain (except when opening and closing the channel). Every time a payment is settled, a new commitment transaction is signed. Such a transaction reflects the current state of the channel and can be broadcast if one of the participant disappears. How many times can a payment channel be used? Payment channels can be used as long as both parties continue to cooperate with each other. Channels do not have any use or time limit. How large is the Lightning Network? The total number of nodes, channels and network capacity has been constantly increasing for quite some time now. You can use 1ml.com to see up-to-date statistics. Keep in mind that some channels are private; they are not advertised across the network so they are not included in those stats. How fast are Lightning Network payments? They are usually instantaneous. Although, some payments might take a few seconds if a wallet needs to try multiple different paths. How often do payments fail? A payment fails if there is no route to the destination or if there is no enough liquidity in the channels in the selected routing path. The latter problem can be mitigated by splitting the payment into few small chunks and sending them through different paths. How high are transaction fees? Most channels charge a base fee and a fee proportional to the amount sent, so the larger the payment, the more you are going to pay. You should pay less than 3 satoshi for transactions <= $10 for most of the time. Are Lightning Network payments more anonymous than on-chain transactions? Yes, Lightning Network payments are more anonymous. They use onion routing. In short, when a payment is being routed, an intermediary node knows only the previous and the next node in the path. It is impossible to tell who initiated the payment and what the final destination is. Wallets Which wallet would be the best for me? There are quite a few interesting options for different kinds of users. No-coiners: Strike Bitcoin newbies: BlueWallet Regular users: Phoenix Wallet, Breez Wallet, Blixt Wallet Advanced users: run your own node Smiley Electrum also has a built-in support for the Lightning Network. Make sure to read Electrum Lightning Network walkthrough if you decide to give it a try. Should I run my own node instead of using some wallet? You could benefit from running your own node in a few ways. Assuming that you would run your node 24/7, you would be able to receive payments at all times. Nodes can also help the network by forwarding payments. You would also be able to take advantage of advanced features like: opening multiple channels in a single transaction, dual-funding and keysend payments. Do I have to generate an invoice every time I want to receive coins over the Lightning Network? No, invoiceless (keysend/spontaneous) payments are supported by LND and c-lightning. Most wallets do not support this feature, though. Why can't I receive coins? Quote from: https://lightning-wallet.com/using-lightning-wallet#using-lightning-wallet In order to receive Lightning payments, some conditions must be met: 1. Nothing can be received immediately after creating a new payment channel, as ‘room’ for incoming funds has to be made by spending some funds first. A payment channel can be thought of as a full bottle of water: in order to pour something in one first has to pour something out. 2. Each channel implicitly contains a reserve which is unspendable and typically takes about 2% of the channel’s capacity. You must spend an amount matching that reserve to make receiving possible. Unspendable channel reserve is the reason you see a negative receive limit when a new channel is full. It indicates how much you need to spend before anything can be received through the channel. 3. Every payment request is disposable, they can’t be fulfilled twice. So you will need to issue a new individual payment request for every incoming payment you wish to receive. 4. Wallet needs to be online in order to receive off-chain funds. Can I receive a payment when I am offline? You need to use a third-party service or a custodial wallet (ex. BlueWallet) for that. Running a node Which implementation should I choose? The most popular implementations are: c-lightning, LND and eclair. Each of them offers slightly different features and third-party plugin/software support. You should research it carefully before making a decision. It is impossible to move existing channels between implementations; you would have to reopen them if you changed your mind. How much money can you make on running a Lightning Network node? Unless you have a lot of coins, your earnings won't be enough to cover both hardware and maintenance costs. If you are already running a full node to support the network then a small Lightning node won't put much stress on your hardware. I have been running a small node (6 channels; ~0.10 BTC capacity) for about 3 months now. I earned over 500 satoshi in the first month during which I was experimenting a lot with my fee settings for each channel. In the second and the third month I earned ~110 and ~160 satoshi respectively without paying much attention to my node. If you want to see up-to-date stats, check out The Lightning Network node experience thread. Does opening new channels help to increase the earnings? Maybe. There are also a few other things that you should take into account: your fee policy, liquidity and the average capacity of your channels. It doesn't make much sense to open channels only to large nodes. They very likely already have large channels between themselves. It might be a good idea to open channels to medium sized nodes which are at the opposite ends of the network. Does my node have to route payments? You can either create private channels which are not advertised across the network or you can set extremely large routing fees for your channels to discourage other people from using them. How do channel owners get paid for routing payments? The routing fee is added to the balance of the person who routes the payment. The total fee charged is calculated as follows: basefee + (amount * feerate / 1000000), where amount is the forwarded amount. Both basefee and feerate can be adjusted individually for every channel. Note that the fee is charged based on the settings of the outgoing channel. Is running a Lightning Network node demanding? Even a Raspberry Pi 3 B+ is capable of running a Lightning Network node. Check out RaspiBlitz, RaspiBolt or Umbrel for fast setup. I used to run a full Bitcoin node and LND on a 2 GB Raspberry Pi 4 and everything was working fine. It might be also a good idea to get a cheap used laptop instead. If you still want to buy a Raspberry Pi then consider paying extra for the latest model which is far more superior in terms of CPU performance. Is there any risk in running a Lightning Network node? Yes, due to many factors. Lightning Network implementations might contain critical bugs which could be exploited to steal funds locked up in channels. A Lightning node is basically a hot wallet. You should not keep any significant amount of coins on it unless you know what you are doing. If you don't keep your node online 24/7, someone can attempt to cheat by broadcasting an old state of your channel. An online node would normally broadcast a penalty transaction. This can be mitigated by the use of watchtowers. Do I have to run a full Bitcoin node? No, LND supports neutrino; c-lightning allows using a pruned node. It might be a bumpy experience, though. Keep in mind that you might encounter some problems if your Lightning software crashes. Your Bitcoin node could delete a block which still hasn't been processed by your Lightning node. How do I backup my channels? You cannot restore your channels from your seed. The backup process varies on the implementation. LND: you should back up your channel.backup file whenever you open a new channel. You can use it to reconnect to your peers and ask them to close the channel forcefully. Note that if the other node is offline or refuses to cooperate, you won't be able to recover your coins. c-lightning: read this; you will probably end up using a backup plugin which maintains a full copy of your channel database. You can keep using your channels after restoring such backup. Can I refill my channel? Currently, it is impossible to refill a channel without the use of third-party services. Splicing is supposed to address this problem. It will allow to increase/decrease the total capacity of the channel without closing it. You can use Boltz, Lightning Conductor, ZigZag to exchange on-chain coins to off-chain ones and vice-versa. How do I balance my channel? You can balance your channel by spending coins from it. See the answer above. You can also use those services to convert your off-chain balance to an on-chain transaction. You can open a dual-funded channel. This feature is currently available only in c-lightning and requires both users to enable it manually. You can also try setting both your base fee and PPM temporarily to zero or some low value to encourage other people to use your channel. Although, you will have no control over the amount of coins that gets moved to the other side in the process. What happens to milisatoshis when the channel is being closed? Example: let's assume that after deducting the fee of the closing transaction, node A is supposed to get 6049.4 sat and node B 10300.6 satoshis. Since Bitcoin blockchain supports only up to 8 decimals, we have to do something about milisatoshis. All such values are rounded down and the remaining 1 satoshi is added to the transaction fee. It is also worth mentioning that if one of the parties' balance is under the dust limit, it is added to the fee instead. Who pays the channel opening and closing transaction fee? The channel opening transaction fee is always paid by the founder of the channel. If the channel is closed cooperatively then the founder also covers the transaction fee. An uncooperative channel close involves two on-chain transactions. If the channel is closed by the other participant then they cover the fee of the second transaction. How does uncooperative channel close work? Quote from: Rath_ on July 06, 2021, 01:00:54 PM First of all, the timelock is decided before the channel is established. By default, most nodes force the other peer to wait 144 blocks (~1 day). The maximum acceptable value by default is 2016 blocks (~2 weeks). I configured my node to create channels with their_to_self_delay = 432 blocks (~3 days), so if someone decides to close the channel opened to my node uncooperatively, they will have to wait 432 blocks (after the commitment transaction has been included in a block) before they can spend the output belonging to them. Those timelocks are relative which means that you do not have to sign a new commitment transaction whenever a new block is mined. New commitment transactions are signed periodically because their fees need to match the current state of the mempool. There is no point in paying 60 sat/vbyte when 1 sat/vbyte transactions are getting confirmed in just a few minutes. It also applies the other way around. The first transaction is the commitment transaction. Let's say there's node A(lice) and node B(ob), and node A broadcasts the commitment transaction. That commitment transaction includes two outputs: - output #0: 3 BTC (spendable by node B's private key) - reflecting node B balance - output #1: 6 BTC (RSMC) - reflecting node A balance There is one more important detail before we go any further. Whenever a new commitment transaction is signed, both parties exchange revocation keys for the previous commitment transaction so that they can both be sure that the other party is very unlikely to broadcast an old state of the channel. RSMC is short for Revocable Sequence Maturing Contract. Such an output contains a relative timelock. This means that you can't spend this output until a certain amount of blocks have been mined since the transaction which includes that output was mined. Let's say node B didn't change the default value of 144 blocks and the commitment transaction has been confirmed. There are two possible scenarios. 1) Node A attempts to cheat and broadcast an old commitment transaction. Node B has 144 blocks to spend the RSMC output using his and node A's revocation key which he got while they were working on a new commitment transaction. 2) Node A broadcasts the latest commitment transaction. In such a case, node B never got node A's revocation key for that commitment transaction, so he cannot spend that RSMC. Node A can broadcast another transaction spending that output after 144 blocks have been mined. Concerns Is the Lightning Network centralized? The common argument is that users are more likely to open channels to large nodes rather than small/medium ones. While that's true, as the networks continues to grow, we can expect hundreds or even thousands of nodes to concentrate end users. This post speculates on possible types of nodes; you should read it if you are still concerned. Can it have a negative impact on the first layer? If many channels are closed at once, the transaction fees could immediately spike and remain high for an extended period of time. Does the Lightning Network solve Bitcoin's scalability problem? Not completely. The Lightning Network was designed mostly for micro-transactions which would not be cost-effective on the first layer. Large payments are also feasible thanks to multi-path payments. Opening a channel involves an on-chain transaction so if we expect every user to open at least one channel, the blockchain would quickly become congested for a long time. Thus, other scaling solutions are needed. Alternatively, more layers can be built on top of the Lightning Network. What would happen if some nodes went temporarily offline? Should many large nodes go offline at the same time, payment failures might become more common. If you have only one channel and your peer goes offline then you obviously won't be able to send and receive any payments. Other questions What shops accept Lightning Network payments? Here you can find a list of merchants who accept LN payments. Do any exchanges support the Lightning Network? Yes, the biggest exchange which supports Lightning deposits and withdrawals is Bitfinex. Here you can find an up-to-date list of exchanges which support the LN. What are the upcoming features? Dual funded channels - both parties will be able to fund a channel. This feature is available in c-lightning (experimentally). Splicing-In & Out - it will be possible to add and remove funds from existing Lightning Network channels without having to close them. Channel factories - existing Lightning Network channels could be used for creating new channels without broadcasting anything to the Bitcoin network. Normally, a channel is opened to only one person. In channel factories, there is a group of people. Group members maintain channels between themselves. More involved users = more savings. If one of the participants is uncooperative, existing channels are not affected - new channels can't be created, though.
json metadata{"tags":["bitcoin"],"links":["https://lightning-wallet.com/using-lightning-wallet#using-lightning-wallet"],"app":"steemit/0.2","format":"markdown"}
Transaction InfoBlock #74232405/Trx 5de39a113b24e871dc8ba4f3b2a02258212b9f75
View Raw JSON Data
{
  "trx_id": "5de39a113b24e871dc8ba4f3b2a02258212b9f75",
  "block": 74232405,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-05-01T06:29:15",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "hive-179944",
      "author": "username",
      "permlink": "the-lightning-network-faq",
      "title": "The Lightning Network FAQ",
      "body": "This thread is now self-moderated. The previous one got derailed. Please, don't discuss here whether or not the Lightning Network is a good scaling solution.\n\nIf you don't know anything about the Lightning Network, consider reading \"Basics of The Lightning Network\" first.\n\nTable of contents\n\n      1. Lightning basics\n      2. Wallets\n      3. Running a node\n      4. Concerns\n      5. Other questions\n\nLightning basics\n\nHow are coins on the Lightning Network different from the on-chain ones?\n\nThey are exactly the same coins. They are stored in a multi-signature address and transactions are settled between two parties without broadcasting anything to the blockchain (except when opening and closing the channel). Every time a payment is settled, a new commitment transaction is signed. Such a transaction reflects the current state of the channel and can be broadcast if one of the participant disappears.\n\n\nHow many times can a payment channel be used?\n\nPayment channels can be used as long as both parties continue to cooperate with each other. Channels do not have any use or time limit.\n\n\nHow large is the Lightning Network?\n\nThe total number of nodes, channels and network capacity has been constantly increasing for quite some time now. You can use 1ml.com to see up-to-date statistics. Keep in mind that some channels are private; they are not advertised across the network so they are not included in those stats.\n\n\nHow fast are Lightning Network payments?\n\nThey are usually instantaneous. Although, some payments might take a few seconds if a wallet needs to try multiple different paths.\n\n\nHow often do payments fail?\n\nA payment fails if there is no route to the destination or if there is no enough liquidity in the channels in the selected routing path. The latter problem can be mitigated by splitting the payment into few small chunks and sending them through different paths.\n\n\nHow high are transaction fees?\n\nMost channels charge a base fee and a fee proportional to the amount sent, so the larger the payment, the more you are going to pay. You should pay less than 3 satoshi for transactions <= $10 for most of the time.\n\n\nAre Lightning Network payments more anonymous than on-chain transactions?\n\nYes, Lightning Network payments are more anonymous. They use onion routing. In short, when a payment is being routed, an intermediary node knows only the previous and the next node in the path. It is impossible to tell who initiated the payment and what the final destination is.\n\n\nWallets\n\nWhich wallet would be the best for me?\n\nThere are quite a few interesting options for different kinds of users.\n\nNo-coiners: Strike\n\nBitcoin newbies: BlueWallet\n\nRegular users: Phoenix Wallet, Breez Wallet, Blixt Wallet\n\nAdvanced users: run your own node Smiley\n\nElectrum also has a built-in support for the Lightning Network. Make sure to read Electrum Lightning Network walkthrough if you decide to give it a try.\n\n\nShould I run my own node instead of using some wallet?\n\nYou could benefit from running your own node in a few ways. Assuming that you would run your node 24/7, you would be able to receive payments at all times. Nodes can also help the network by forwarding payments. You would also be able to take advantage of advanced features like: opening multiple channels in a single transaction, dual-funding and keysend payments.\n\n\nDo I have to generate an invoice every time I want to receive coins over the Lightning Network?\n\nNo, invoiceless (keysend/spontaneous) payments are supported by LND and c-lightning. Most wallets do not support this feature, though.\n\n\nWhy can't I receive coins?\n\nQuote from: https://lightning-wallet.com/using-lightning-wallet#using-lightning-wallet\nIn order to receive Lightning payments, some conditions must be met:\n\n1. Nothing can be received immediately after creating a new payment channel, as ‘room’ for incoming funds has to be made by spending some funds first. A payment channel can be thought of as a full bottle of water: in order to pour something in one first has to pour something out.\n\n2. Each channel implicitly contains a reserve which is unspendable and typically takes about 2% of the channel’s capacity. You must spend an amount matching that reserve to make receiving possible. Unspendable channel reserve is the reason you see a negative receive limit when a new channel is full. It indicates how much you need to spend before anything can be received through the channel.\n\n3. Every payment request is disposable, they can’t be fulfilled twice. So you will need to issue a new individual payment request for every incoming payment you wish to receive.\n\n4. Wallet needs to be online in order to receive off-chain funds.\n\n\nCan I receive a payment when I am offline?\n\nYou need to use a third-party service or a custodial wallet (ex. BlueWallet) for that.\n\n\nRunning a node\n\nWhich implementation should I choose?\n\nThe most popular implementations are: c-lightning, LND and eclair. Each of them offers slightly different features and third-party plugin/software support. You should research it carefully before making a decision. It is impossible to move existing channels between implementations; you would have to reopen them if you changed your mind.\n\n\nHow much money can you make on running a Lightning Network node?\n\nUnless you have a lot of coins, your earnings won't be enough to cover both hardware and maintenance costs. If you are already running a full node to support the network then a small Lightning node won't put much stress on your hardware.\n\nI have been running a small node (6 channels; ~0.10 BTC capacity) for about 3 months now. I earned over 500 satoshi in the first month during which I was experimenting a lot with my fee settings for each channel. In the second and the third month I earned ~110 and ~160 satoshi respectively without paying much attention to my node. If you want to see up-to-date stats, check out The Lightning Network node experience thread.\n\n\nDoes opening new channels help to increase the earnings?\n\nMaybe. There are also a few other things that you should take into account: your fee policy, liquidity and the average capacity of your channels. It doesn't make much sense to open channels only to large nodes. They very likely already have large channels between themselves. It might be a good idea to open channels to medium sized nodes which are at the opposite ends of the network.\n\n\nDoes my node have to route payments?\n\nYou can either create private channels which are not advertised across the network or you can set extremely large routing fees for your channels to discourage other people from using them.\n\n\nHow do channel owners get paid for routing payments?\n\nThe routing fee is added to the balance of the person who routes the payment. The total fee charged is calculated as follows: basefee + (amount * feerate / 1000000), where amount is the forwarded amount. Both basefee and feerate can be adjusted individually for every channel. Note that the fee is charged based on the settings of the outgoing channel.\n\n\nIs running a Lightning Network node demanding?\n\nEven a Raspberry Pi 3 B+ is capable of running a Lightning Network node. Check out RaspiBlitz, RaspiBolt or Umbrel for fast setup. I used to run a full Bitcoin node and LND on a 2 GB Raspberry Pi 4 and everything was working fine. It might be also a good idea to get a cheap used laptop instead. If you still want to buy a Raspberry Pi then consider paying extra for the latest model which is far more superior in terms of CPU performance.\n\n\nIs there any risk in running a Lightning Network node?\n\nYes, due to many factors. Lightning Network implementations might contain critical bugs which could be exploited to steal funds locked up in channels. A Lightning node is basically a hot wallet. You should not keep any significant amount of coins on it unless you know what you are doing.\n\nIf you don't keep your node online 24/7, someone can attempt to cheat by broadcasting an old state of your channel. An online node would normally broadcast a penalty transaction. This can be mitigated by the use of watchtowers.\n\n\nDo I have to run a full Bitcoin node?\n\nNo, LND supports neutrino; c-lightning allows using a pruned node. It might be a bumpy experience, though. Keep in mind that you might encounter some problems if your Lightning software crashes. Your Bitcoin node could delete a block which still hasn't been processed by your Lightning node.\n\n\nHow do I backup my channels?\n\nYou cannot restore your channels from your seed. The backup process varies on the implementation.\n\nLND: you should back up your channel.backup file whenever you open a new channel. You can use it to reconnect to your peers and ask them to close the channel forcefully. Note that if the other node is offline or refuses to cooperate, you won't be able to recover your coins.\n\nc-lightning: read this; you will probably end up using a backup plugin which maintains a full copy of your channel database. You can keep using your channels after restoring such backup.\n\n\nCan I refill my channel?\n\nCurrently, it is impossible to refill a channel without the use of third-party services. Splicing is supposed to address this problem. It will allow to increase/decrease the total capacity of the channel without closing it.\n\nYou can use Boltz, Lightning Conductor, ZigZag to exchange on-chain coins to off-chain ones and vice-versa.\n\n\nHow do I balance my channel?\n\nYou can balance your channel by spending coins from it. See the answer above. You can also use those services to convert your off-chain balance to an on-chain transaction.\n\nYou can open a dual-funded channel. This feature is currently available only in c-lightning and requires both users to enable it manually.\n\nYou can also try setting both your base fee and PPM temporarily to zero or some low value to encourage other people to use your channel. Although, you will have no control over the amount of coins that gets moved to the other side in the process.\n\n\nWhat happens to milisatoshis when the channel is being closed?\n\nExample: let's assume that after deducting the fee of the closing transaction, node A is supposed to get 6049.4 sat and node B 10300.6 satoshis. Since Bitcoin blockchain supports only up to 8 decimals, we have to do something about milisatoshis. All such values are rounded down and the remaining 1 satoshi is added to the transaction fee.\n\nIt is also worth mentioning that if one of the parties' balance is under the dust limit, it is added to the fee instead.\n\n\nWho pays the channel opening and closing transaction fee?\n\nThe channel opening transaction fee is always paid by the founder of the channel. If the channel is closed cooperatively then the founder also covers the transaction fee. An uncooperative channel close involves two on-chain transactions. If the channel is closed by the other participant then they cover the fee of the second transaction.\n\n\nHow does uncooperative channel close work?\n\nQuote from: Rath_ on July 06, 2021, 01:00:54 PM\nFirst of all, the timelock is decided before the channel is established. By default, most nodes force the other peer to wait 144 blocks (~1 day). The maximum acceptable value by default is 2016 blocks (~2 weeks). I configured my node to create channels with their_to_self_delay = 432 blocks (~3 days), so if someone decides to close the channel opened to my node uncooperatively, they will have to wait 432 blocks (after the commitment transaction has been included in a block) before they can spend the output belonging to them. Those timelocks are relative which means that you do not have to sign a new commitment transaction whenever a new block is mined. New commitment transactions are signed periodically because their fees need to match the current state of the mempool. There is no point in paying 60 sat/vbyte when 1 sat/vbyte transactions are getting confirmed in just a few minutes. It also applies the other way around.\n\nThe first transaction is the commitment transaction. Let's say there's node A(lice) and node B(ob), and node A broadcasts the commitment transaction. That commitment transaction includes two outputs:\n\n- output #0: 3 BTC (spendable by node B's private key) - reflecting node B balance\n- output #1: 6 BTC (RSMC) - reflecting node A balance\n\nThere is one more important detail before we go any further. Whenever a new commitment transaction is signed, both parties exchange revocation keys for the previous commitment transaction so that they can both be sure that the other party is very unlikely to broadcast an old state of the channel.\n\nRSMC is short for Revocable Sequence Maturing Contract. Such an output contains a relative timelock. This means that you can't spend this output until a certain amount of blocks have been mined since the transaction which includes that output was mined.\n\nLet's say node B didn't change the default value of 144 blocks and the commitment transaction has been confirmed. There are two possible scenarios.\n\n1) Node A attempts to cheat and broadcast an old commitment transaction. Node B has 144 blocks to spend the RSMC output using his and node A's revocation key which he got while they were working on a new commitment transaction.\n\n2) Node A broadcasts the latest commitment transaction. In such a case, node B never got node A's revocation key for that commitment transaction, so he cannot spend that RSMC. Node A can broadcast another transaction spending that output after 144 blocks have been mined.\n\n\nConcerns\n\nIs the Lightning Network centralized?\n\nThe common argument is that users are more likely to open channels to large nodes rather than small/medium ones. While that's true, as the networks continues to grow, we can expect hundreds or even thousands of nodes to concentrate end users. This post speculates on possible types of nodes; you should read it if you are still concerned.\n\n\nCan it have a negative impact on the first layer?\n\nIf many channels are closed at once, the transaction fees could immediately spike and remain high for an extended period of time.\n\n\nDoes the Lightning Network solve Bitcoin's scalability problem?\n\nNot completely. The Lightning Network was designed mostly for micro-transactions which would not be cost-effective on the first layer. Large payments are also feasible thanks to multi-path payments. Opening a channel involves an on-chain transaction so if we expect every user to open at least one channel, the blockchain would quickly become congested for a long time. Thus, other scaling solutions are needed. Alternatively, more layers can be built on top of the Lightning Network.\n\n\nWhat would happen if some nodes went temporarily offline?\n\nShould many large nodes go offline at the same time, payment failures might become more common. If you have only one channel and your peer goes offline then you obviously won't be able to send and receive any payments.\n\n\nOther questions\n\n\nWhat shops accept Lightning Network payments?\n\nHere you can find a list of merchants who accept LN payments.\n\n\nDo any exchanges support the Lightning Network?\n\nYes, the biggest exchange which supports Lightning deposits and withdrawals is Bitfinex. Here you can find an up-to-date list of exchanges which support the LN.\n\n\nWhat are the upcoming features?\n\nDual funded channels - both parties will be able to fund a channel. This feature is available in c-lightning (experimentally).\n\nSplicing-In & Out - it will be possible to add and remove funds from existing Lightning Network channels without having to close them.\n\nChannel factories - existing Lightning Network channels could be used for creating new channels without broadcasting anything to the Bitcoin network. Normally, a channel is opened to only one person. In channel factories, there is a group of people. Group members maintain channels between themselves. More involved users = more savings. If one of the participants is uncooperative, existing channels are not affected - new channels can't be created, though.",
      "json_metadata": "{\"tags\":[\"bitcoin\"],\"links\":[\"https://lightning-wallet.com/using-lightning-wallet#using-lightning-wallet\"],\"app\":\"steemit/0.2\",\"format\":\"markdown\"}"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 818223451.691 . Total Dividend Payout 94.754 . Date 2023-04-19 21:56:54.047216+08:00"
2023/04/19 13:56:57
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 818223451.691 . Total Dividend Payout 94.754 . Date 2023-04-19 21:56:54.047216+08:00
Transaction InfoBlock #73899917/Trx 6bb1d2ac5b2935c3c084dfabad42230320d6f745
View Raw JSON Data
{
  "trx_id": "6bb1d2ac5b2935c3c084dfabad42230320d6f745",
  "block": 73899917,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-04-19T13:56:57",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 818223451.691 . Total Dividend Payout 94.754 . Date 2023-04-19 21:56:54.047216+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 823159395.123 . Total Dividend Payout 152.94 . Date 2023-01-04 21:42:50.201236+08:00"
2023/01/04 13:42:54
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 823159395.123 . Total Dividend Payout 152.94 . Date 2023-01-04 21:42:50.201236+08:00
Transaction InfoBlock #70890194/Trx 0b19182f93680f698bc5e9aee731a41d4b0ebf47
View Raw JSON Data
{
  "trx_id": "0b19182f93680f698bc5e9aee731a41d4b0ebf47",
  "block": 70890194,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-01-04T13:42:54",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 823159395.123 . Total Dividend Payout 152.94 . Date 2023-01-04 21:42:50.201236+08:00"
    }
  ]
}
epicdicesent 0.004 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 825327216.305 . Total Dividend Payout 383.605 . Date 2022-12-14 21:43:02.331525+08:00"
2022/12/14 13:43:06
fromepicdice
tousername
amount0.004 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 825327216.305 . Total Dividend Payout 383.605 . Date 2022-12-14 21:43:02.331525+08:00
Transaction InfoBlock #70290323/Trx 8db089b05b9a2e99bb3082e7eecd39e14d31b1e3
View Raw JSON Data
{
  "trx_id": "8db089b05b9a2e99bb3082e7eecd39e14d31b1e3",
  "block": 70290323,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-12-14T13:43:06",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.004 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 825327216.305 . Total Dividend Payout 383.605 . Date 2022-12-14 21:43:02.331525+08:00"
    }
  ]
}
2022/12/12 00:19:00
voterdilums
authorusername
permlinkdark-net-market-list
weight10000 (100.00%)
Transaction InfoBlock #70216955/Trx fc31ffa0065b14cb04740a4914ddfe89e0ec6b67
View Raw JSON Data
{
  "trx_id": "fc31ffa0065b14cb04740a4914ddfe89e0ec6b67",
  "block": 70216955,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-12-12T00:19:00",
  "op": [
    "vote",
    {
      "voter": "dilums",
      "author": "username",
      "permlink": "dark-net-market-list",
      "weight": 10000
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 829595574.173 . Total Dividend Payout 113.03 . Date 2022-12-04 21:34:53.102327+08:00"
2022/12/04 13:34:57
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 829595574.173 . Total Dividend Payout 113.03 . Date 2022-12-04 21:34:53.102327+08:00
Transaction InfoBlock #70003431/Trx 2fd27850c8b9ea2ba6859762eb8ba088bcbec330
View Raw JSON Data
{
  "trx_id": "2fd27850c8b9ea2ba6859762eb8ba088bcbec330",
  "block": 70003431,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-12-04T13:34:57",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 829595574.173 . Total Dividend Payout 113.03 . Date 2022-12-04 21:34:53.102327+08:00"
    }
  ]
}
epicdicesent 0.004 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832009246.217 . Total Dividend Payout 328.194 . Date 2022-12-01 21:32:06.948220+08:00"
2022/12/01 13:32:09
fromepicdice
tousername
amount0.004 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832009246.217 . Total Dividend Payout 328.194 . Date 2022-12-01 21:32:06.948220+08:00
Transaction InfoBlock #69917616/Trx 84f0d3a545b98fe76b29c4106143b46aad989b8c
View Raw JSON Data
{
  "trx_id": "84f0d3a545b98fe76b29c4106143b46aad989b8c",
  "block": 69917616,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-12-01T13:32:09",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.004 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832009246.217 . Total Dividend Payout 328.194 . Date 2022-12-01 21:32:06.948220+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 831845604.289 . Total Dividend Payout 276.976 . Date 2022-11-30 21:35:46.436113+08:00"
2022/11/30 13:35:48
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 831845604.289 . Total Dividend Payout 276.976 . Date 2022-11-30 21:35:46.436113+08:00
Transaction InfoBlock #69889040/Trx 0de21890b9d0928b8d9392e5de0d78a90a69c8ac
View Raw JSON Data
{
  "trx_id": "0de21890b9d0928b8d9392e5de0d78a90a69c8ac",
  "block": 69889040,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-30T13:35:48",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 831845604.289 . Total Dividend Payout 276.976 . Date 2022-11-30 21:35:46.436113+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830742328.677 . Total Dividend Payout 165.51 . Date 2022-11-27 21:31:07.933646+08:00"
2022/11/27 13:31:12
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830742328.677 . Total Dividend Payout 165.51 . Date 2022-11-27 21:31:07.933646+08:00
Transaction InfoBlock #69803424/Trx 4cf535496588ba1389b34683df6a4ca5bdf12c03
View Raw JSON Data
{
  "trx_id": "4cf535496588ba1389b34683df6a4ca5bdf12c03",
  "block": 69803424,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-27T13:31:12",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830742328.677 . Total Dividend Payout 165.51 . Date 2022-11-27 21:31:07.933646+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830590481.313 . Total Dividend Payout 96.459 . Date 2022-11-26 21:29:20.939090+08:00"
2022/11/26 13:29:24
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830590481.313 . Total Dividend Payout 96.459 . Date 2022-11-26 21:29:20.939090+08:00
Transaction InfoBlock #69774708/Trx 69840beb9146a25d54bc812f2968cf9623420233
View Raw JSON Data
{
  "trx_id": "69840beb9146a25d54bc812f2968cf9623420233",
  "block": 69774708,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-26T13:29:24",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830590481.313 . Total Dividend Payout 96.459 . Date 2022-11-26 21:29:20.939090+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830770359.91 . Total Dividend Payout 123.224 . Date 2022-11-25 21:27:53.546867+08:00"
2022/11/25 13:27:57
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830770359.91 . Total Dividend Payout 123.224 . Date 2022-11-25 21:27:53.546867+08:00
Transaction InfoBlock #69746003/Trx 3a1d21560ce9bcf8d6bdcf91af2010c37be53b1e
View Raw JSON Data
{
  "trx_id": "3a1d21560ce9bcf8d6bdcf91af2010c37be53b1e",
  "block": 69746003,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-25T13:27:57",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 830770359.91 . Total Dividend Payout 123.224 . Date 2022-11-25 21:27:53.546867+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832718118.466 . Total Dividend Payout 271.731 . Date 2022-11-23 21:30:48.617049+08:00"
2022/11/23 13:30:51
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832718118.466 . Total Dividend Payout 271.731 . Date 2022-11-23 21:30:48.617049+08:00
Transaction InfoBlock #69688725/Trx 37580c2ceee559dfbb8d38dbf82fe4e086f36c03
View Raw JSON Data
{
  "trx_id": "37580c2ceee559dfbb8d38dbf82fe4e086f36c03",
  "block": 69688725,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-23T13:30:51",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832718118.466 . Total Dividend Payout 271.731 . Date 2022-11-23 21:30:48.617049+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832636410.231 . Total Dividend Payout 127.163 . Date 2022-11-14 21:24:25.871925+08:00"
2022/11/14 13:24:27
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832636410.231 . Total Dividend Payout 127.163 . Date 2022-11-14 21:24:25.871925+08:00
Transaction InfoBlock #69430649/Trx 1938971f2f6c784a2695113a403f8e64d328b14a
View Raw JSON Data
{
  "trx_id": "1938971f2f6c784a2695113a403f8e64d328b14a",
  "block": 69430649,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-14T13:24:27",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 832636410.231 . Total Dividend Payout 127.163 . Date 2022-11-14 21:24:25.871925+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 834663438.618 . Total Dividend Payout 179.755 . Date 2022-11-04 21:20:07.289765+08:00"
2022/11/04 13:20:09
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 9367.656 , Circulating Supply 834663438.618 . Total Dividend Payout 179.755 . Date 2022-11-04 21:20:07.289765+08:00
Transaction InfoBlock #69143879/Trx 0471c9da2449d86da48226ce6a91361c54a2b8bf
View Raw JSON Data
{
  "trx_id": "0471c9da2449d86da48226ce6a91361c54a2b8bf",
  "block": 69143879,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-04T13:20:09",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 9367.656 , Circulating Supply 834663438.618 . Total Dividend Payout 179.755 . Date 2022-11-04 21:20:07.289765+08:00"
    }
  ]
}
usernamesent 125.000 STEEM to @deepcrypto8- "100157559"
2022/03/25 23:54:15
fromusername
todeepcrypto8
amount125.000 STEEM
memo100157559
Transaction InfoBlock #62742637/Trx bbd4a960170dd47052d130d5e8d94e2772aaa11d
View Raw JSON Data
{
  "trx_id": "bbd4a960170dd47052d130d5e8d94e2772aaa11d",
  "block": 62742637,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-03-25T23:54:15",
  "op": [
    "transfer",
    {
      "from": "username",
      "to": "deepcrypto8",
      "amount": "125.000 STEEM",
      "memo": "100157559"
    }
  ]
}
usernamecustom json: community
2022/03/17 05:07:27
required auths[]
required posting auths["username"]
idcommunity
json["subscribe",{"community":"hive-179944"}]
Transaction InfoBlock #62490934/Trx bfed8ad3847fdfcf2e8805287ae4e252d0ba36db
View Raw JSON Data
{
  "trx_id": "bfed8ad3847fdfcf2e8805287ae4e252d0ba36db",
  "block": 62490934,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-03-17T05:07:27",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "username"
      ],
      "id": "community",
      "json": "[\"subscribe\",{\"community\":\"hive-179944\"}]"
    }
  ]
}
usernamecreated a new account: @hive-179944
2022/03/17 05:07:18
fee3.000 STEEM
creatorusername
new account namehive-179944
owner{"weight_threshold":1,"account_auths":[],"key_auths":[["STM5EQD9WMe9C6W5X7XMuzz5hQfNnaYgNbhGn82Xrs19G52hQr6ps",1]]}
active{"weight_threshold":1,"account_auths":[],"key_auths":[["STM5hMtDiHhr5fcSnEeiKaJ4TpyJKZc7sXVZLF9zTckTsgE7y2spH",1]]}
posting{"weight_threshold":1,"account_auths":[],"key_auths":[["STM4uwq8cevAF2YBGz6GqG5jbkewvHZsDHDNExh84Vvv5gvqcLh9j",1]]}
memo keySTM7gwvPiAsG2RsrdEpTTZpXzskPjL8zvgppSquf7Y6teMDWic2RQ
json metadata
Transaction InfoBlock #62490931/Trx 9db150b1685edc9af6f0858f6bfa4aa9b143ea0d
View Raw JSON Data
{
  "trx_id": "9db150b1685edc9af6f0858f6bfa4aa9b143ea0d",
  "block": 62490931,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-03-17T05:07:18",
  "op": [
    "account_create",
    {
      "fee": "3.000 STEEM",
      "creator": "username",
      "new_account_name": "hive-179944",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM5EQD9WMe9C6W5X7XMuzz5hQfNnaYgNbhGn82Xrs19G52hQr6ps",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM5hMtDiHhr5fcSnEeiKaJ4TpyJKZc7sXVZLF9zTckTsgE7y2spH",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM4uwq8cevAF2YBGz6GqG5jbkewvHZsDHDNExh84Vvv5gvqcLh9j",
            1
          ]
        ]
      },
      "memo_key": "STM7gwvPiAsG2RsrdEpTTZpXzskPjL8zvgppSquf7Y6teMDWic2RQ",
      "json_metadata": ""
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 849344868.357 . Total Dividend Payout 601.805 . Date 2022-02-22 22:31:23.420013+08:00"
2022/02/22 14:31:24
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 849344868.357 . Total Dividend Payout 601.805 . Date 2022-02-22 22:31:23.420013+08:00
Transaction InfoBlock #61843074/Trx c02e1df727a582d45e5d36bc06fcb227ac996641
View Raw JSON Data
{
  "trx_id": "c02e1df727a582d45e5d36bc06fcb227ac996641",
  "block": 61843074,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-22T14:31:24",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 849344868.357 . Total Dividend Payout 601.805 . Date 2022-02-22 22:31:23.420013+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 819447242.432 . Total Dividend Payout 579.021 . Date 2022-02-15 22:15:56.988394+08:00"
2022/02/15 14:16:00
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 819447242.432 . Total Dividend Payout 579.021 . Date 2022-02-15 22:15:56.988394+08:00
Transaction InfoBlock #61644051/Trx b6615ecfa4b42b58f957a7cfd9bc0414cb50061c
View Raw JSON Data
{
  "trx_id": "b6615ecfa4b42b58f957a7cfd9bc0414cb50061c",
  "block": 61644051,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-15T14:16:00",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 819447242.432 . Total Dividend Payout 579.021 . Date 2022-02-15 22:15:56.988394+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818864642.927 . Total Dividend Payout 664.525 . Date 2022-02-14 22:14:46.222511+08:00"
2022/02/14 14:14:48
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818864642.927 . Total Dividend Payout 664.525 . Date 2022-02-14 22:14:46.222511+08:00
Transaction InfoBlock #61615373/Trx cd9fb02dc2c836ea41419af4531bce3827a475b7
View Raw JSON Data
{
  "trx_id": "cd9fb02dc2c836ea41419af4531bce3827a475b7",
  "block": 61615373,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-14T14:14:48",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818864642.927 . Total Dividend Payout 664.525 . Date 2022-02-14 22:14:46.222511+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818329718.235 . Total Dividend Payout 1060.208 . Date 2022-02-13 22:15:57.344224+08:00"
2022/02/13 14:15:57
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818329718.235 . Total Dividend Payout 1060.208 . Date 2022-02-13 22:15:57.344224+08:00
Transaction InfoBlock #61586746/Trx 6fe4935c5f90b0a1a5f47abc0cb321d2fc6458bb
View Raw JSON Data
{
  "trx_id": "6fe4935c5f90b0a1a5f47abc0cb321d2fc6458bb",
  "block": 61586746,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-13T14:15:57",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 818329718.235 . Total Dividend Payout 1060.208 . Date 2022-02-13 22:15:57.344224+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 814450356.412 . Total Dividend Payout 446.309 . Date 2022-02-12 22:13:26.741475+08:00"
2022/02/12 14:13:27
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 814450356.412 . Total Dividend Payout 446.309 . Date 2022-02-12 22:13:26.741475+08:00
Transaction InfoBlock #61558085/Trx c1cc064eedb9f0ff366616820c9e5a78094e6470
View Raw JSON Data
{
  "trx_id": "c1cc064eedb9f0ff366616820c9e5a78094e6470",
  "block": 61558085,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-12T14:13:27",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 814450356.412 . Total Dividend Payout 446.309 . Date 2022-02-12 22:13:26.741475+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 808398187.959 . Total Dividend Payout 704.577 . Date 2022-02-10 22:12:26.840374+08:00"
2022/02/10 14:12:30
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 808398187.959 . Total Dividend Payout 704.577 . Date 2022-02-10 22:12:26.840374+08:00
Transaction InfoBlock #61500870/Trx a612b318297a53bf830a3050a8bb55b964686679
View Raw JSON Data
{
  "trx_id": "a612b318297a53bf830a3050a8bb55b964686679",
  "block": 61500870,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-10T14:12:30",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 808398187.959 . Total Dividend Payout 704.577 . Date 2022-02-10 22:12:26.840374+08:00"
    }
  ]
}
epicdicesent 0.006 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 795765595.451 . Total Dividend Payout 1896.185 . Date 2022-02-08 22:16:24.653618+08:00"
2022/02/08 14:16:27
fromepicdice
tousername
amount0.006 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 795765595.451 . Total Dividend Payout 1896.185 . Date 2022-02-08 22:16:24.653618+08:00
Transaction InfoBlock #61443643/Trx 302853cfc4b05a548dff8fc483866a95614fe7cd
View Raw JSON Data
{
  "trx_id": "302853cfc4b05a548dff8fc483866a95614fe7cd",
  "block": 61443643,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-02-08T14:16:27",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.006 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 795765595.451 . Total Dividend Payout 1896.185 . Date 2022-02-08 22:16:24.653618+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 777208291.808 . Total Dividend Payout 551.478 . Date 2022-01-30 22:07:29.968688+08:00"
2022/01/30 14:07:30
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 777208291.808 . Total Dividend Payout 551.478 . Date 2022-01-30 22:07:29.968688+08:00
Transaction InfoBlock #61185606/Trx 596c1747016252955b8f93c736eb3c970e45795d
View Raw JSON Data
{
  "trx_id": "596c1747016252955b8f93c736eb3c970e45795d",
  "block": 61185606,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-30T14:07:30",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 777208291.808 . Total Dividend Payout 551.478 . Date 2022-01-30 22:07:29.968688+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 776883178.099 . Total Dividend Payout 429.357 . Date 2022-01-29 22:05:43.291647+08:00"
2022/01/29 14:05:45
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 776883178.099 . Total Dividend Payout 429.357 . Date 2022-01-29 22:05:43.291647+08:00
Transaction InfoBlock #61156922/Trx bbfef9aadc7b534ed5590880858ac449e62af2e2
View Raw JSON Data
{
  "trx_id": "bbfef9aadc7b534ed5590880858ac449e62af2e2",
  "block": 61156922,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-29T14:05:45",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 776883178.099 . Total Dividend Payout 429.357 . Date 2022-01-29 22:05:43.291647+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 775423529.827 . Total Dividend Payout 569.961 . Date 2022-01-25 22:03:04.321018+08:00"
2022/01/25 14:03:06
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 775423529.827 . Total Dividend Payout 569.961 . Date 2022-01-25 22:03:04.321018+08:00
Transaction InfoBlock #61042285/Trx 9be706fde4b707a86c1a8ea108f52a09fffde320
View Raw JSON Data
{
  "trx_id": "9be706fde4b707a86c1a8ea108f52a09fffde320",
  "block": 61042285,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-25T14:03:06",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 775423529.827 . Total Dividend Payout 569.961 . Date 2022-01-25 22:03:04.321018+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 774125736.447 . Total Dividend Payout 417.402 . Date 2022-01-23 22:01:57.800844+08:00"
2022/01/23 14:02:00
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 774125736.447 . Total Dividend Payout 417.402 . Date 2022-01-23 22:01:57.800844+08:00
Transaction InfoBlock #60984966/Trx c09aea2ce920b89dfae939aa77eda7460489aee6
View Raw JSON Data
{
  "trx_id": "c09aea2ce920b89dfae939aa77eda7460489aee6",
  "block": 60984966,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-23T14:02:00",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 774125736.447 . Total Dividend Payout 417.402 . Date 2022-01-23 22:01:57.800844+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 772093198.142 . Total Dividend Payout 534.664 . Date 2022-01-15 22:02:24.174407+08:00"
2022/01/15 14:02:27
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 772093198.142 . Total Dividend Payout 534.664 . Date 2022-01-15 22:02:24.174407+08:00
Transaction InfoBlock #60755794/Trx 9966877b67728c9d53d080ae138265eb19e31a2b
View Raw JSON Data
{
  "trx_id": "9966877b67728c9d53d080ae138265eb19e31a2b",
  "block": 60755794,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-15T14:02:27",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 772093198.142 . Total Dividend Payout 534.664 . Date 2022-01-15 22:02:24.174407+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771627904.888 . Total Dividend Payout 335.333 . Date 2022-01-14 22:04:32.581803+08:00"
2022/01/14 14:04:33
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771627904.888 . Total Dividend Payout 335.333 . Date 2022-01-14 22:04:32.581803+08:00
Transaction InfoBlock #60727193/Trx dc16b34b068a4ab14b1e86cfb99158742a1e3ba1
View Raw JSON Data
{
  "trx_id": "dc16b34b068a4ab14b1e86cfb99158742a1e3ba1",
  "block": 60727193,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-14T14:04:33",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771627904.888 . Total Dividend Payout 335.333 . Date 2022-01-14 22:04:32.581803+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 770656324.197 . Total Dividend Payout 530.16 . Date 2022-01-13 21:59:59.509414+08:00"
2022/01/13 14:00:00
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 770656324.197 . Total Dividend Payout 530.16 . Date 2022-01-13 21:59:59.509414+08:00
Transaction InfoBlock #60698458/Trx a8e0d0095caa93a07667047dda344b8ea022338d
View Raw JSON Data
{
  "trx_id": "a8e0d0095caa93a07667047dda344b8ea022338d",
  "block": 60698458,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-13T14:00:00",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 770656324.197 . Total Dividend Payout 530.16 . Date 2022-01-13 21:59:59.509414+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771440990.197 . Total Dividend Payout 750.652 . Date 2022-01-09 21:57:25.557388+08:00"
2022/01/09 13:57:27
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771440990.197 . Total Dividend Payout 750.652 . Date 2022-01-09 21:57:25.557388+08:00
Transaction InfoBlock #60583830/Trx b22825cad136cc6d332445577fbe2ef365fd2e08
View Raw JSON Data
{
  "trx_id": "b22825cad136cc6d332445577fbe2ef365fd2e08",
  "block": 60583830,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-09T13:57:27",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 771440990.197 . Total Dividend Payout 750.652 . Date 2022-01-09 21:57:25.557388+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768993984.713 . Total Dividend Payout 353.853 . Date 2022-01-05 21:52:17.208605+08:00"
2022/01/05 13:52:18
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768993984.713 . Total Dividend Payout 353.853 . Date 2022-01-05 21:52:17.208605+08:00
Transaction InfoBlock #60469268/Trx 827c7914cb749e2410739931d94d62356e78f4fe
View Raw JSON Data
{
  "trx_id": "827c7914cb749e2410739931d94d62356e78f4fe",
  "block": 60469268,
  "trx_in_block": 23,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-05T13:52:18",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768993984.713 . Total Dividend Payout 353.853 . Date 2022-01-05 21:52:17.208605+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768657002.191 . Total Dividend Payout 394.35 . Date 2022-01-03 21:53:51.392068+08:00"
2022/01/03 13:53:54
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768657002.191 . Total Dividend Payout 394.35 . Date 2022-01-03 21:53:51.392068+08:00
Transaction InfoBlock #60412015/Trx 9893d90f73756b8de9eaccf9e73b30a76c7fd660
View Raw JSON Data
{
  "trx_id": "9893d90f73756b8de9eaccf9e73b30a76c7fd660",
  "block": 60412015,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-03T13:53:54",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 768657002.191 . Total Dividend Payout 394.35 . Date 2022-01-03 21:53:51.392068+08:00"
    }
  ]
}
brad3840sent 0.737 SBD to @username- "41360bd2-34b2-45c3-b838-7c3fef1c028b"
2021/09/26 18:29:12
frombrad3840
tousername
amount0.737 SBD
memo41360bd2-34b2-45c3-b838-7c3fef1c028b
Transaction InfoBlock #57594390/Trx af2c3f868d0298b9a3902cd77a13c55747efcf92
View Raw JSON Data
{
  "trx_id": "af2c3f868d0298b9a3902cd77a13c55747efcf92",
  "block": 57594390,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-09-26T18:29:12",
  "op": [
    "transfer",
    {
      "from": "brad3840",
      "to": "username",
      "amount": "0.737 SBD",
      "memo": "41360bd2-34b2-45c3-b838-7c3fef1c028b"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1020744477.141 . Total Dividend Payout 540.601 . Date 2021-08-15 21:47:50.790726+08:00"
2021/08/15 13:47:51
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1020744477.141 . Total Dividend Payout 540.601 . Date 2021-08-15 21:47:50.790726+08:00
Transaction InfoBlock #56388135/Trx 8080023f80632830815333ce36551e8e7dcb50f2
View Raw JSON Data
{
  "trx_id": "8080023f80632830815333ce36551e8e7dcb50f2",
  "block": 56388135,
  "trx_in_block": 39,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-08-15T13:47:51",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1020744477.141 . Total Dividend Payout 540.601 . Date 2021-08-15 21:47:50.790726+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1026851338.641 . Total Dividend Payout 457.038 . Date 2021-07-07 21:43:40.189480+08:00"
2021/07/07 13:43:42
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1026851338.641 . Total Dividend Payout 457.038 . Date 2021-07-07 21:43:40.189480+08:00
Transaction InfoBlock #55275146/Trx 689bc840bb5838c111d19dc496478df5fe03f1e2
View Raw JSON Data
{
  "trx_id": "689bc840bb5838c111d19dc496478df5fe03f1e2",
  "block": 55275146,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-07T13:43:42",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1026851338.641 . Total Dividend Payout 457.038 . Date 2021-07-07 21:43:40.189480+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1023714157.196 . Total Dividend Payout 443.82 . Date 2021-07-01 21:43:55.205995+08:00"
2021/07/01 13:43:57
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1023714157.196 . Total Dividend Payout 443.82 . Date 2021-07-01 21:43:55.205995+08:00
Transaction InfoBlock #55103535/Trx 49083110251359d0d5df96a5bac81136ed2978bb
View Raw JSON Data
{
  "trx_id": "49083110251359d0d5df96a5bac81136ed2978bb",
  "block": 55103535,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-07-01T13:43:57",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1023714157.196 . Total Dividend Payout 443.82 . Date 2021-07-01 21:43:55.205995+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1016995120.749 . Total Dividend Payout 526.83 . Date 2021-04-25 21:37:37.778664+08:00"
2021/04/25 13:37:39
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1016995120.749 . Total Dividend Payout 526.83 . Date 2021-04-25 21:37:37.778664+08:00
Transaction InfoBlock #53194506/Trx 037223055d215e57637ad26e701a94a4857fb283
View Raw JSON Data
{
  "trx_id": "037223055d215e57637ad26e701a94a4857fb283",
  "block": 53194506,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-25T13:37:39",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1016995120.749 . Total Dividend Payout 526.83 . Date 2021-04-25 21:37:37.778664+08:00"
    }
  ]
}
swaguureplied to @username / qrtwta
2021/04/19 20:56:00
parent authorusername
parent permlinkhow-i-earned-some-bitcoin-and-steem-using-this-arbitrage-trading-method-within-minutes
authorswaguu
permlinkqrtwta
title
bodyInterested @steemit,@steem,@bitcoin
json metadata{"users":["steemit","steem","bitcoin"],"app":"steemit/0.2"}
Transaction InfoBlock #53032166/Trx 5d3c482edc3efe5742c5a525f979e3829b3818a4
View Raw JSON Data
{
  "trx_id": "5d3c482edc3efe5742c5a525f979e3829b3818a4",
  "block": 53032166,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-19T20:56:00",
  "op": [
    "comment",
    {
      "parent_author": "username",
      "parent_permlink": "how-i-earned-some-bitcoin-and-steem-using-this-arbitrage-trading-method-within-minutes",
      "author": "swaguu",
      "permlink": "qrtwta",
      "title": "",
      "body": "Interested @steemit,@steem,@bitcoin",
      "json_metadata": "{\"users\":[\"steemit\",\"steem\",\"bitcoin\"],\"app\":\"steemit/0.2\"}"
    }
  ]
}
2021/04/19 20:54:03
voterswaguu
authorusername
permlinkdark-net-market-list
weight-10000 (-100.00%)
Transaction InfoBlock #53032129/Trx 88d365a3af53c2c6e3bf6677acd4d78b26420f05
View Raw JSON Data
{
  "trx_id": "88d365a3af53c2c6e3bf6677acd4d78b26420f05",
  "block": 53032129,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-19T20:54:03",
  "op": [
    "vote",
    {
      "voter": "swaguu",
      "author": "username",
      "permlink": "dark-net-market-list",
      "weight": -10000
    }
  ]
}
2021/04/19 20:53:45
voterswaguu
authorusername
permlinkdark-net-market-list
weight10000 (100.00%)
Transaction InfoBlock #53032123/Trx ee3c0d2109b6129480d92051e6df13df7e692043
View Raw JSON Data
{
  "trx_id": "ee3c0d2109b6129480d92051e6df13df7e692043",
  "block": 53032123,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-19T20:53:45",
  "op": [
    "vote",
    {
      "voter": "swaguu",
      "author": "username",
      "permlink": "dark-net-market-list",
      "weight": 10000
    }
  ]
}
2021/04/19 20:53:33
voterswaguu
authorusername
permlinkdark-net-market-list
weight-10000 (-100.00%)
Transaction InfoBlock #53032119/Trx 1755ce4f0ecf2faf4816c45392b3dba3a38922e9
View Raw JSON Data
{
  "trx_id": "1755ce4f0ecf2faf4816c45392b3dba3a38922e9",
  "block": 53032119,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-04-19T20:53:33",
  "op": [
    "vote",
    {
      "voter": "swaguu",
      "author": "username",
      "permlink": "dark-net-market-list",
      "weight": -10000
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1019157696.795 . Total Dividend Payout 622.906 . Date 2021-03-02 21:35:04.419764+08:00"
2021/03/02 13:35:06
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1019157696.795 . Total Dividend Payout 622.906 . Date 2021-03-02 21:35:04.419764+08:00
Transaction InfoBlock #51661577/Trx a40af0722b2d4ac3effaf0b50ee7303e6331c007
View Raw JSON Data
{
  "trx_id": "a40af0722b2d4ac3effaf0b50ee7303e6331c007",
  "block": 51661577,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-03-02T13:35:06",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 2317.656 , Circulating Supply 1019157696.795 . Total Dividend Payout 622.906 . Date 2021-03-02 21:35:04.419764+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1004108579.313 . Total Dividend Payout 1593.799 . Date 2021-01-31 21:36:19.606113+08:00"
2021/01/31 13:36:21
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1004108579.313 . Total Dividend Payout 1593.799 . Date 2021-01-31 21:36:19.606113+08:00
Transaction InfoBlock #50808792/Trx 47bd2956f4921626197fb25fbd8370eee6052f3b
View Raw JSON Data
{
  "trx_id": "47bd2956f4921626197fb25fbd8370eee6052f3b",
  "block": 50808792,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-31T13:36:21",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1004108579.313 . Total Dividend Payout 1593.799 . Date 2021-01-31 21:36:19.606113+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1000321618.211 . Total Dividend Payout 1971.783 . Date 2021-01-30 21:34:34.164006+08:00"
2021/01/30 13:34:36
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1000321618.211 . Total Dividend Payout 1971.783 . Date 2021-01-30 21:34:34.164006+08:00
Transaction InfoBlock #50780272/Trx 70d6f590280f1e297a3342cf280face5d5fbc342
View Raw JSON Data
{
  "trx_id": "70d6f590280f1e297a3342cf280face5d5fbc342",
  "block": 50780272,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-30T13:34:36",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 1000321618.211 . Total Dividend Payout 1971.783 . Date 2021-01-30 21:34:34.164006+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 998095718.116 . Total Dividend Payout 787.316 . Date 2021-01-29 21:34:40.887749+08:00"
2021/01/29 13:34:42
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 998095718.116 . Total Dividend Payout 787.316 . Date 2021-01-29 21:34:40.887749+08:00
Transaction InfoBlock #50751778/Trx a965b34249982b84c58f630496e038cc003ce6b1
View Raw JSON Data
{
  "trx_id": "a965b34249982b84c58f630496e038cc003ce6b1",
  "block": 50751778,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-29T13:34:42",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 998095718.116 . Total Dividend Payout 787.316 . Date 2021-01-29 21:34:40.887749+08:00"
    }
  ]
}
epicdicesent 0.005 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 986375708.91 . Total Dividend Payout 2882.125 . Date 2021-01-28 21:34:58.419954+08:00"
2021/01/28 13:35:00
fromepicdice
tousername
amount0.005 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 986375708.91 . Total Dividend Payout 2882.125 . Date 2021-01-28 21:34:58.419954+08:00
Transaction InfoBlock #50723314/Trx 1946f300e416d2b99126b7f7d11dbc05d5ee25e3
View Raw JSON Data
{
  "trx_id": "1946f300e416d2b99126b7f7d11dbc05d5ee25e3",
  "block": 50723314,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-28T13:35:00",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.005 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 986375708.91 . Total Dividend Payout 2882.125 . Date 2021-01-28 21:34:58.419954+08:00"
    }
  ]
}
epicdicesent 0.003 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 960192327.974 . Total Dividend Payout 1941.106 . Date 2021-01-24 21:36:40.768530+08:00"
2021/01/24 13:36:42
fromepicdice
tousername
amount0.003 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 960192327.974 . Total Dividend Payout 1941.106 . Date 2021-01-24 21:36:40.768530+08:00
Transaction InfoBlock #50609477/Trx 4e5433604c41bb669319dd28a4b2aff4ad7a2fc1
View Raw JSON Data
{
  "trx_id": "4e5433604c41bb669319dd28a4b2aff4ad7a2fc1",
  "block": 50609477,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-24T13:36:42",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.003 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 960192327.974 . Total Dividend Payout 1941.106 . Date 2021-01-24 21:36:40.768530+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 935205163.506 . Total Dividend Payout 1082.592 . Date 2021-01-16 21:34:59.946776+08:00"
2021/01/16 13:35:03
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 935205163.506 . Total Dividend Payout 1082.592 . Date 2021-01-16 21:34:59.946776+08:00
Transaction InfoBlock #50381643/Trx 6db7b5464300b8373bb1639a8a6920b5089f4a9d
View Raw JSON Data
{
  "trx_id": "6db7b5464300b8373bb1639a8a6920b5089f4a9d",
  "block": 50381643,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-16T13:35:03",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 935205163.506 . Total Dividend Payout 1082.592 . Date 2021-01-16 21:34:59.946776+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 933282302.277 . Total Dividend Payout 1044.633 . Date 2021-01-15 21:36:32.497775+08:00"
2021/01/15 13:36:33
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 933282302.277 . Total Dividend Payout 1044.633 . Date 2021-01-15 21:36:32.497775+08:00
Transaction InfoBlock #50353224/Trx 789355d71c974470ab7a4f52294720040ebaa96a
View Raw JSON Data
{
  "trx_id": "789355d71c974470ab7a4f52294720040ebaa96a",
  "block": 50353224,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-15T13:36:33",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 933282302.277 . Total Dividend Payout 1044.633 . Date 2021-01-15 21:36:32.497775+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 927161131.335 . Total Dividend Payout 1077.822 . Date 2021-01-10 21:34:23.954589+08:00"
2021/01/10 13:34:24
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 927161131.335 . Total Dividend Payout 1077.822 . Date 2021-01-10 21:34:23.954589+08:00
Transaction InfoBlock #50210817/Trx cca5b39bff82ce4a3277c76188c56ec2db41370c
View Raw JSON Data
{
  "trx_id": "cca5b39bff82ce4a3277c76188c56ec2db41370c",
  "block": 50210817,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-10T13:34:24",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 927161131.335 . Total Dividend Payout 1077.822 . Date 2021-01-10 21:34:23.954589+08:00"
    }
  ]
}
epicdicesent 0.002 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 926095595.851 . Total Dividend Payout 877.895 . Date 2021-01-09 21:51:01.052923+08:00"
2021/01/09 13:51:06
fromepicdice
tousername
amount0.002 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 926095595.851 . Total Dividend Payout 877.895 . Date 2021-01-09 21:51:01.052923+08:00
Transaction InfoBlock #50182665/Trx 4fdc733d17bcfb2faa8590f083a623c0ee707610
View Raw JSON Data
{
  "trx_id": "4fdc733d17bcfb2faa8590f083a623c0ee707610",
  "block": 50182665,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-01-09T13:51:06",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 926095595.851 . Total Dividend Payout 877.895 . Date 2021-01-09 21:51:01.052923+08:00"
    }
  ]
}
epicdicesent 0.001 STEEM to @username- "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 898543864.637 . Total Dividend Payout 681.222 . Date 2020-12-14 21:34:04.395859+08:00"
2020/12/14 13:34:06
fromepicdice
tousername
amount0.001 STEEM
memo[Dividend] EPC Token quantity 1594.271 , Circulating Supply 898543864.637 . Total Dividend Payout 681.222 . Date 2020-12-14 21:34:04.395859+08:00
Transaction InfoBlock #49442895/Trx 5dea0bb53b045baaf1c220ffa45555f441810484
View Raw JSON Data
{
  "trx_id": "5dea0bb53b045baaf1c220ffa45555f441810484",
  "block": 49442895,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-14T13:34:06",
  "op": [
    "transfer",
    {
      "from": "epicdice",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Dividend] EPC Token quantity 1594.271 , Circulating Supply 898543864.637 . Total Dividend Payout 681.222 . Date 2020-12-14 21:34:04.395859+08:00"
    }
  ]
}
epictokensent 0.046 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-07-07 21:00:19.359973+08:00"
2020/07/07 13:00:21
fromepictoken
tousername
amount0.046 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-07-07 21:00:19.359973+08:00
Transaction InfoBlock #44898767/Trx 5099309b7a4dbae18f01c236aaf8fb315e4b6fe3
View Raw JSON Data
{
  "trx_id": "5099309b7a4dbae18f01c236aaf8fb315e4b6fe3",
  "block": 44898767,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-07-07T13:00:21",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.046 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-07-07 21:00:19.359973+08:00"
    }
  ]
}
epictokensent 0.001 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-07-05 21:00:23.936212+08:00"
2020/07/05 13:00:27
fromepictoken
tousername
amount0.001 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-07-05 21:00:23.936212+08:00
Transaction InfoBlock #44841712/Trx 072d925a6e23292b8eaaed1920d5d74b056ec4f6
View Raw JSON Data
{
  "trx_id": "072d925a6e23292b8eaaed1920d5d74b056ec4f6",
  "block": 44841712,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-07-05T13:00:27",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-07-05 21:00:23.936212+08:00"
    }
  ]
}
epictokensent 0.013 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-07-02 21:00:19.519458+08:00"
2020/07/02 13:00:21
fromepictoken
tousername
amount0.013 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-07-02 21:00:19.519458+08:00
Transaction InfoBlock #44756137/Trx f9d325ab65bda00815c9dadf65fc434055061d87
View Raw JSON Data
{
  "trx_id": "f9d325ab65bda00815c9dadf65fc434055061d87",
  "block": 44756137,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-07-02T13:00:21",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.013 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-07-02 21:00:19.519458+08:00"
    }
  ]
}
epictokensent 0.048 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-06-20 21:00:16.018741+08:00"
2020/06/20 13:00:18
fromepictoken
tousername
amount0.048 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-06-20 21:00:16.018741+08:00
Transaction InfoBlock #44414030/Trx 116a7784c12539d06c527734d8d6fcbf59b72df9
View Raw JSON Data
{
  "trx_id": "116a7784c12539d06c527734d8d6fcbf59b72df9",
  "block": 44414030,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-06-20T13:00:18",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.048 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-06-20 21:00:16.018741+08:00"
    }
  ]
}
epictokensent 0.015 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-06-06 21:00:21.385236+08:00"
2020/06/06 13:00:24
fromepictoken
tousername
amount0.015 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-06-06 21:00:21.385236+08:00
Transaction InfoBlock #44016039/Trx e56ac833c47ffece2fe2cb69b93c5a9628542659
View Raw JSON Data
{
  "trx_id": "e56ac833c47ffece2fe2cb69b93c5a9628542659",
  "block": 44016039,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-06-06T13:00:24",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.015 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-06-06 21:00:21.385236+08:00"
    }
  ]
}
epictokensent 0.002 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-06-05 21:00:30.844820+08:00"
2020/06/05 13:00:33
fromepictoken
tousername
amount0.002 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-06-05 21:00:30.844820+08:00
Transaction InfoBlock #43987665/Trx 9da3b2cd693de1ba01628f6e6a7e5d6f6d35e4db
View Raw JSON Data
{
  "trx_id": "9da3b2cd693de1ba01628f6e6a7e5d6f6d35e4db",
  "block": 43987665,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-06-05T13:00:33",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-06-05 21:00:30.844820+08:00"
    }
  ]
}
epictokensent 0.004 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-05-24 21:00:25.804114+08:00"
2020/05/24 13:00:30
fromepictoken
tousername
amount0.004 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-05-24 21:00:25.804114+08:00
Transaction InfoBlock #43648144/Trx 507cebc4d66d78e18902021d63ec3fc8e56d9a7e
View Raw JSON Data
{
  "trx_id": "507cebc4d66d78e18902021d63ec3fc8e56d9a7e",
  "block": 43648144,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-24T13:00:30",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.004 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-05-24 21:00:25.804114+08:00"
    }
  ]
}
epictokensent 0.002 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-05-21 21:00:29.977342+08:00"
2020/05/21 13:00:33
fromepictoken
tousername
amount0.002 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-05-21 21:00:29.977342+08:00
Transaction InfoBlock #43563423/Trx 12a287b62dc8b134056af7122189c0576c3716a9
View Raw JSON Data
{
  "trx_id": "12a287b62dc8b134056af7122189c0576c3716a9",
  "block": 43563423,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-21T13:00:33",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.002 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-05-21 21:00:29.977342+08:00"
    }
  ]
}
epictokensent 0.005 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-05-20 21:00:26.382145+08:00"
2020/05/20 13:00:27
fromepictoken
tousername
amount0.005 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-05-20 21:00:26.382145+08:00
Transaction InfoBlock #43535108/Trx 1087306f310e8aa5445d424d0e0e60e9252326c0
View Raw JSON Data
{
  "trx_id": "1087306f310e8aa5445d424d0e0e60e9252326c0",
  "block": 43535108,
  "trx_in_block": 49,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-20T13:00:27",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.005 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-05-20 21:00:26.382145+08:00"
    }
  ]
}
epictokensent 0.004 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-05-17 21:00:58.851973+08:00"
2020/05/17 13:01:03
fromepictoken
tousername
amount0.004 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-05-17 21:00:58.851973+08:00
Transaction InfoBlock #43450813/Trx 02de512af93b98553e2ac9ae12e92bd899f499fe
View Raw JSON Data
{
  "trx_id": "02de512af93b98553e2ac9ae12e92bd899f499fe",
  "block": 43450813,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-17T13:01:03",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.004 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-05-17 21:00:58.851973+08:00"
    }
  ]
}
epictokensent 0.001 STEEM to @username- "[Rewards] Epicdice's referral, Date : 2020-05-11 21:00:20.697067+08:00"
2020/05/11 13:00:24
fromepictoken
tousername
amount0.001 STEEM
memo[Rewards] Epicdice's referral, Date : 2020-05-11 21:00:20.697067+08:00
Transaction InfoBlock #43281836/Trx 844a66d58ca2ee0c4ccde0fe0c04fc68ccc4f63e
View Raw JSON Data
{
  "trx_id": "844a66d58ca2ee0c4ccde0fe0c04fc68ccc4f63e",
  "block": 43281836,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-11T13:00:24",
  "op": [
    "transfer",
    {
      "from": "epictoken",
      "to": "username",
      "amount": "0.001 STEEM",
      "memo": "[Rewards] Epicdice's referral, Date : 2020-05-11 21:00:20.697067+08:00"
    }
  ]
}

Account Metadata

POSTING JSON METADATA
None
JSON METADATA
None
{
  "posting_json_metadata": {},
  "json_metadata": {}
}

Auth Keys

Owner
Single Signature
Public Keys
STM7xYJJhtUon7SPZV195rnCt8UsCCzh8g5K9PDsrU2kLMBKCQ4Jo1/1
Active
Single Signature
Public Keys
STM5MDv7gmhHA1K9W7DQdfx9jtZZGmhT5c1SKqDXaMod8Z32REXPM1/1
Posting
Single Signature
Public Keys
STM6GZczjf8yYR5ST8Sy2vopEu34J5YgJyLxMSCMLAXKc9juXXi3M1/1
Memo
STM7x4Q2rZdkC7QZNiKdGcLnvZFMkFSSRmJtrCr7WyfjmLpGYQiPt
{
  "owner": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM7xYJJhtUon7SPZV195rnCt8UsCCzh8g5K9PDsrU2kLMBKCQ4Jo",
        1
      ]
    ]
  },
  "active": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM5MDv7gmhHA1K9W7DQdfx9jtZZGmhT5c1SKqDXaMod8Z32REXPM",
        1
      ]
    ]
  },
  "posting": {
    "weight_threshold": 1,
    "account_auths": [],
    "key_auths": [
      [
        "STM6GZczjf8yYR5ST8Sy2vopEu34J5YgJyLxMSCMLAXKc9juXXi3M",
        1
      ]
    ]
  },
  "memo": "STM7x4Q2rZdkC7QZNiKdGcLnvZFMkFSSRmJtrCr7WyfjmLpGYQiPt"
}

Witness Votes

0 / 30
No active witness votes.
[]