Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fde67683969de5a30471ca5d8b47acbb356a13e09f2b09d41cfc691fd1367cfb

Tx prefix hash: d4af9ce080108a66cf8cb780d6fcb443dc46ce16de8edc09c63eb41750d6ac4e
Tx public key: 5943642cfee5e96b45d703821380a6b5dcef29e0dcb8fcc4776a76132ac54571
Timestamp: 1738630481 Timestamp [UCT]: 2025-02-04 00:54:41 Age [y:d:h:m:s]: 00:290:23:27:19
Block: 1211581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205724 RingCT/type: yes/0
Extra: 015943642cfee5e96b45d703821380a6b5dcef29e0dcb8fcc4776a76132ac54571021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbea9a82cc9a7f62818f4dc52d9e780581da7cc58499f07dcbe363a0d032fb7f 0.600000000000 1698344 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": 1211591, "vin": [ { "gen": { "height": 1211581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbea9a82cc9a7f62818f4dc52d9e780581da7cc58499f07dcbe363a0d032fb7f" } } ], "extra": [ 1, 89, 67, 100, 44, 254, 229, 233, 107, 69, 215, 3, 130, 19, 128, 166, 181, 220, 239, 41, 224, 220, 184, 252, 196, 119, 106, 118, 19, 42, 197, 69, 113, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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