Transaction: 296bfb99ec4ef8396c87ad8fe0f84f8e24dd9934

Included in block 22,457,357 at 2018/05/15 17:12:30 (UTC).

Transaction overview

Loading...
Transaction info
transaction_id 296bfb99ec4ef8396c87ad8fe0f84f8e24dd9934
ref_block_num 44,028
block_num22,457,357
ref_block_prefix 1,841,895,445
expiration2018/05/15T17:22:27
transaction_num 51
extensions[]
signatures 1f593edcd1bf26183ecf813643fb2bfa1f2040a92c7ef87fdd356e935ca2427157063afea72442064a29682d208cc4ee5f395f24bbf83a1536db7443e1a444568b
operations
comment
"parent_author":"numpypython",<br>"parent_permlink":"using-bookie-odds-as-a-starting-point",<br>"author":"acelad",<br>"permlink":"re-numpypython-using-bookie-odds-as-a-starting-point-20180515t171228134z",<br>"title":"",<br>"body":"Great post @numpypython! \n\nLooking at how teams have performed at certain odds ranges is something I do often. I haven't figured out yet whether it's better to use **odds ranges** or **current league position**,<br> but I would expect them to yield roughly the same results. I plan to do some testing however in this area!",<br>"json_metadata":" \"tags\":[\"sports\" ,<br>\"users\":[\"numpypython\" ,<br>\"app\":\"steemit\/0.1\" "
* The API used to generate this page is provided by @steemchiller.