Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fb0d5f044878e00463a886b5087fcbc61719f0a612377eabe6ef9c77dc13260

Tx prefix hash: 987add200764c020b47281a29f98c9e482e619d635c125a34ada3fdb8a300cd9
Tx public key: 68d7f0387ccc64c69dcdc16f6e8065286c4cc1b7a50fa76afb7513527bbb65eb
Timestamp: 1580977728 Timestamp [UCT]: 2020-02-06 08:28:48 Age [y:d:h:m:s]: 04:334:03:11:48
Block: 59738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130263 RingCT/type: yes/0
Extra: 0168d7f0387ccc64c69dcdc16f6e8065286c4cc1b7a50fa76afb7513527bbb65eb0211000000037adf42d3000000000000000000

1 output(s) for total of 389.102504586000 dcy

stealth address amount amount idx
00: b818fdd682422f7c5035d43d1b79554b88d3c251881547113f5eb289d87cfa21 389.102504586000 110234 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": 59748, "vin": [ { "gen": { "height": 59738 } } ], "vout": [ { "amount": 389102504586, "target": { "key": "b818fdd682422f7c5035d43d1b79554b88d3c251881547113f5eb289d87cfa21" } } ], "extra": [ 1, 104, 215, 240, 56, 124, 204, 100, 198, 157, 205, 193, 111, 110, 128, 101, 40, 108, 76, 193, 183, 165, 15, 167, 106, 251, 117, 19, 82, 123, 187, 101, 235, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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