Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3dcbf2c3a03f2026698bf812c427bad7f2967da5f2aad26aaeccf48ffa32ecd

Tx prefix hash: 983eb5b6ccf1a68e4053c8861c56ddc28025d0985c6253cb8d59f436a931ac51
Tx public key: e23eda8a795d2748938d093e06ed19e369b13ec802b0c8f8235a11855aa97a1b
Timestamp: 1719153514 Timestamp [UCT]: 2024-06-23 14:38:34 Age [y:d:h:m:s]: 01:140:14:04:20
Block: 1050522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359037 RingCT/type: yes/0
Extra: 01e23eda8a795d2748938d093e06ed19e369b13ec802b0c8f8235a11855aa97a1b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c91e0748e67e35679c2f3ec42352396e7f610d5d921fc488442e346151b353 0.600000000000 1520697 of 15

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": 1050532, "vin": [ { "gen": { "height": 1050522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c91e0748e67e35679c2f3ec42352396e7f610d5d921fc488442e346151b353" } } ], "extra": [ 1, 226, 62, 218, 138, 121, 93, 39, 72, 147, 141, 9, 62, 6, 237, 25, 227, 105, 177, 62, 200, 2, 176, 200, 248, 35, 90, 17, 133, 90, 169, 122, 27, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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