Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef375fc6ab1fd185615603a4aea7662bd3aeb79af6d4c6e69b6fd6b8919c2ed9

Tx prefix hash: 6a60c6e9e21e5e2b2432e4b29d90a17914d81665a7f156c3a7107c51cb052a5d
Tx public key: 6472cbb267dd2645787edfdd3af567e0cc9780ee562012286977d33608bddc53
Timestamp: 1577709681 Timestamp [UCT]: 2019-12-30 12:41:21 Age [y:d:h:m:s]: 05:018:00:19:22
Block: 35024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1162873 RingCT/type: yes/0
Extra: 016472cbb267dd2645787edfdd3af567e0cc9780ee562012286977d33608bddc5302110000000a8a2ee0d9000000000000000000

1 output(s) for total of 469.878594567000 dcy

stealth address amount amount idx
00: 34f759f814150afe956c5f571f4c07af57930a692143e5e73be654fb67e02ec0 469.878594567000 59007 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": 35034, "vin": [ { "gen": { "height": 35024 } } ], "vout": [ { "amount": 469878594567, "target": { "key": "34f759f814150afe956c5f571f4c07af57930a692143e5e73be654fb67e02ec0" } } ], "extra": [ 1, 100, 114, 203, 178, 103, 221, 38, 69, 120, 126, 223, 221, 58, 245, 103, 224, 204, 151, 128, 238, 86, 32, 18, 40, 105, 119, 211, 54, 8, 189, 220, 83, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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