Transaction: cca923e539f5efbc900074813ddad84ce2bdadd9

Included in block 5,857,310 at 2016/10/15 15:41:48 (UTC).

Transaction overview

Loading...
Transaction info
transaction_id cca923e539f5efbc900074813ddad84ce2bdadd9
ref_block_num 24,259
block_num5,857,310
ref_block_prefix 3,684,467,554
expiration2016/10/15T15:42:00
transaction_num 2
extensions[]
signatures 203abde0637ba0b0b712d3b849a9f0c88b608bf7b21edbaa38764de6c00c0596be416587f064ff71c2ab83dcf5c3bc914d22d3083df71bcef48ad5bcbad141d732
operations
comment
"parent_author":"dragosroua",<br>"parent_permlink":"timeless-content-versus-timely-content-or-how-steemit-can-lock-itself-out-of-business-in-one-easy-step",<br>"author":"everittdmickey",<br>"permlink":"re-dragosroua-timeless-content-versus-timely-content-or-how-steemit-can-lock-itself-out-of-business-in-one-easy-step-20161015t153055434z",<br>"title":"",<br>"body":"@@ -24,<br>16 +24,<br>388 @@\n y thing.\n+ I don't understand why they complicate things for themselves. Geeks I guess. The %22if it's not broke fix it until it is.%22 syndrome. I see no need for %22payouts%22 to be broken up into two discrete time frames then canceled after that.%0A%0AWhy not pay as you go? When post get's an upvote..credit the account,<br> forever,<br> any time there is a vote.%0A. Why be complicated about it?\n %0AI think\n",<br>"json_metadata":" \"tags\":[\"business\" "
* The API used to generate this page is provided by @steemchiller.