Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1752c10eecd5fa391c4a44a8026aa8b758c374b4b88a6d5a4aeac66a0b1d928c

Tx prefix hash: 50d136e6720da1ce33399f0fec8c9cab67997ee0e2795bb9166ea080c22b9e96
Tx public key: 3ccddd15afa8fa59465f7a3d85c7aa5ec6509c63695e68f95d110cfe63a4ca02
Timestamp: 1577777356 Timestamp [UCT]: 2019-12-31 07:29:16 Age [y:d:h:m:s]: 04:363:07:23:49
Block: 35532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148832 RingCT/type: yes/0
Extra: 013ccddd15afa8fa59465f7a3d85c7aa5ec6509c63695e68f95d110cfe63a4ca020211000000148a2ee0d9000000000000000000

1 output(s) for total of 468.024500177000 dcy

stealth address amount amount idx
00: 38750965125af7f43467716726438aa18c51be2916793210cf9f6eeb1acf35c4 468.024500177000 59976 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": 35542, "vin": [ { "gen": { "height": 35532 } } ], "vout": [ { "amount": 468024500177, "target": { "key": "38750965125af7f43467716726438aa18c51be2916793210cf9f6eeb1acf35c4" } } ], "extra": [ 1, 60, 205, 221, 21, 175, 168, 250, 89, 70, 95, 122, 61, 133, 199, 170, 94, 198, 80, 156, 99, 105, 94, 104, 249, 93, 17, 12, 254, 99, 164, 202, 2, 2, 17, 0, 0, 0, 20, 138, 46, 224, 217, 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