Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5124677c2b72036e65da0a156bb5eed61f70a6d843e6b4ee359960679b1a709b

Tx prefix hash: eef7698e687457e6549c67918db04132f81fce099d1c67a3e6f10ac5b046a928
Tx public key: 76a59642ee82a321d3d0521d1a7733706c8cd88b554afff74e825634c7c207b2
Timestamp: 1577180589 Timestamp [UCT]: 2019-12-24 09:43:09 Age [y:d:h:m:s]: 05:041:08:17:13
Block: 30559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179387 RingCT/type: yes/0
Extra: 0176a59642ee82a321d3d0521d1a7733706c8cd88b554afff74e825634c7c207b2021100000002d81c26c0000000000000000000

1 output(s) for total of 486.123044136000 dcy

stealth address amount amount idx
00: 36a2c78710752ab6f1a6dca37421a719681ea76bf0a4c0c80e49d9acb1e273bc 486.123044136000 50463 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 30569, "vin": [ { "gen": { "height": 30559 } } ], "vout": [ { "amount": 486123044136, "target": { "key": "36a2c78710752ab6f1a6dca37421a719681ea76bf0a4c0c80e49d9acb1e273bc" } } ], "extra": [ 1, 118, 165, 150, 66, 238, 130, 163, 33, 211, 208, 82, 29, 26, 119, 51, 112, 108, 140, 216, 139, 85, 74, 255, 247, 78, 130, 86, 52, 199, 194, 7, 178, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8