Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0cdda6c1f2e64168bf7ed3912c86f326bceac7f141da124a2a7bb98d5ee5de

Tx prefix hash: ff604f1f79f4f8bedf9f779ade1db692a2e3cf18c2adbdb6235596906a09c09e
Tx public key: 9cd7d3a3007cc34c310b5ab5f7d24997414589566444b222d816f93380a9e90f
Timestamp: 1695589190 Timestamp [UCT]: 2023-09-24 20:59:50 Age [y:d:h:m:s]: 01:194:00:56:28
Block: 855376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399740 RingCT/type: yes/0
Extra: 019cd7d3a3007cc34c310b5ab5f7d24997414589566444b222d816f93380a9e90f021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.899050894000 dcy

stealth address amount amount idx
00: 857155745f93531975ceb73e898994f049f20e13dc9457b7976d32ec7c8b8073 0.899050894000 1309394 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": 855386, "vin": [ { "gen": { "height": 855376 } } ], "vout": [ { "amount": 899050894, "target": { "key": "857155745f93531975ceb73e898994f049f20e13dc9457b7976d32ec7c8b8073" } } ], "extra": [ 1, 156, 215, 211, 163, 0, 124, 195, 76, 49, 11, 90, 181, 247, 210, 73, 151, 65, 69, 137, 86, 100, 68, 178, 34, 216, 22, 249, 51, 128, 169, 233, 15, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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