Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89bac21dea61df5ec610da2395e5337f9cab0627cbe2330149ad3db58f9116a5

Tx prefix hash: a5299ea55ffd5df982b1ebce6872859e5b317e6d750e06e11b024d9751d8d2bd
Tx public key: 0a0f7f3c1768b939659800dcf6f84d5d70af146583df7f246efaeceeb4ec36a7
Timestamp: 1574576785 Timestamp [UCT]: 2019-11-24 06:26:25 Age [y:d:h:m:s]: 05:045:18:45:58
Block: 16241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1175582 RingCT/type: yes/0
Extra: 010a0f7f3c1768b939659800dcf6f84d5d70af146583df7f246efaeceeb4ec36a7021100000006f95225a5000000000000000000

1 output(s) for total of 542.235200436000 dcy

stealth address amount amount idx
00: 1e740da636faa0bacd11377308e496f445074c370fea635d6345f48087075680 542.235200436000 22545 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": 16251, "vin": [ { "gen": { "height": 16241 } } ], "vout": [ { "amount": 542235200436, "target": { "key": "1e740da636faa0bacd11377308e496f445074c370fea635d6345f48087075680" } } ], "extra": [ 1, 10, 15, 127, 60, 23, 104, 185, 57, 101, 152, 0, 220, 246, 248, 77, 93, 112, 175, 20, 101, 131, 223, 127, 36, 110, 250, 236, 238, 180, 236, 54, 167, 2, 17, 0, 0, 0, 6, 249, 82, 37, 165, 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