Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1af6554f29d7bcfad864e35408b8c8e5b854f4a024788e6c244da98cdaad869b

Tx prefix hash: 5a742b6d172b1d75c0f7f4e0b687edf941f4ba5a7731b9f2cf012a16b29b2a81
Tx public key: 50295fb9435a1d3051adc59d6c5370515a773c2d0a192b78ac5a16c96d30e9a6
Timestamp: 1621799138 Timestamp [UCT]: 2021-05-23 19:45:38 Age [y:d:h:m:s]: 03:255:16:16:17
Block: 265798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 944682 RingCT/type: yes/0
Extra: 0150295fb9435a1d3051adc59d6c5370515a773c2d0a192b78ac5a16c96d30e9a60211000000156e2c823c000000000000000000

1 output(s) for total of 80.780949701000 dcy

stealth address amount amount idx
00: 5dd2be924fda60176a70f0c98dfad11c381725d1dec92334428759e918e99340 80.780949701000 558646 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": 265808, "vin": [ { "gen": { "height": 265798 } } ], "vout": [ { "amount": 80780949701, "target": { "key": "5dd2be924fda60176a70f0c98dfad11c381725d1dec92334428759e918e99340" } } ], "extra": [ 1, 80, 41, 95, 185, 67, 90, 29, 48, 81, 173, 197, 157, 108, 83, 112, 81, 90, 119, 60, 45, 10, 25, 43, 120, 172, 90, 22, 201, 109, 48, 233, 166, 2, 17, 0, 0, 0, 21, 110, 44, 130, 60, 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