Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4972ebd6ebdcd9b6cdb3a8014adf3e0d6ad38b3be0ae267dad7c1af37503dbb0

Tx prefix hash: 64d8316b4d06fa5cfe68f374fe3818cf403fe613625f3d4c09653e4e11ba6039
Tx public key: 01db3343dd67cbecffc336f007adcee5feed24a8e2fb69f1c16e1d5242de88c7
Timestamp: 1583531736 Timestamp [UCT]: 2020-03-06 21:55:36 Age [y:d:h:m:s]: 04:336:21:13:25
Block: 77684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135146 RingCT/type: yes/0
Extra: 0101db3343dd67cbecffc336f007adcee5feed24a8e2fb69f1c16e1d5242de88c702110000000aa3671f4b000000000000000000

1 output(s) for total of 339.313745527000 dcy

stealth address amount amount idx
00: 2c5a37610fd08af1fd74a3e4d1f6829307a6d3e7df0c2bef852fddc7628df92e 339.313745527000 142847 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": 77694, "vin": [ { "gen": { "height": 77684 } } ], "vout": [ { "amount": 339313745527, "target": { "key": "2c5a37610fd08af1fd74a3e4d1f6829307a6d3e7df0c2bef852fddc7628df92e" } } ], "extra": [ 1, 1, 219, 51, 67, 221, 103, 203, 236, 255, 195, 54, 240, 7, 173, 206, 229, 254, 237, 36, 168, 226, 251, 105, 241, 193, 110, 29, 82, 66, 222, 136, 199, 2, 17, 0, 0, 0, 10, 163, 103, 31, 75, 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