Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8282c474e91a9ee8bbdfde7e64d02136defe305ab9a8b908c9471830fb5b9777

Tx prefix hash: 50a114121d68d2c51a3eb8089573ba27bdb0bf7b38f6a16b9345ee380bde5306
Tx public key: cda0ea8dbd4cd4357e72ef56893c68173d8dd01a0c759d6c2272d38572d1a8f0
Timestamp: 1721368861 Timestamp [UCT]: 2024-07-19 06:01:01 Age [y:d:h:m:s]: 00:283:16:12:46
Block: 1068922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202666 RingCT/type: yes/0
Extra: 01cda0ea8dbd4cd4357e72ef56893c68173d8dd01a0c759d6c2272d38572d1a8f0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71cd1b655367ea1cd3b4d5a2f4691150c7967b04780d8344248f93ef83100f6f 0.600000000000 1540141 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": 1068932, "vin": [ { "gen": { "height": 1068922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71cd1b655367ea1cd3b4d5a2f4691150c7967b04780d8344248f93ef83100f6f" } } ], "extra": [ 1, 205, 160, 234, 141, 189, 76, 212, 53, 126, 114, 239, 86, 137, 60, 104, 23, 61, 141, 208, 26, 12, 117, 157, 108, 34, 114, 211, 133, 114, 209, 168, 240, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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