Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c611af4144964fb72541130d276b86fe5ff19d8fb8c935375753531771d1bdb4

Tx prefix hash: 23408da43d3c93a68bfe7ddc124612a02b4f00d6eab6a341df26fb09e9d63c46
Tx public key: a93c702b773ba9c7a64877ab3e33cdc840dd79bad5a9624629830cfa8911a777
Timestamp: 1669312010 Timestamp [UCT]: 2022-11-24 17:46:50 Age [y:d:h:m:s]: 02:189:04:47:31
Block: 638223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656985 RingCT/type: yes/0
Extra: 01a93c702b773ba9c7a64877ab3e33cdc840dd79bad5a9624629830cfa8911a7770211000000038b7b6602000000000000000000

1 output(s) for total of 4.713052373000 dcy

stealth address amount amount idx
00: e91c9768378e6b48a4ed80e8dc33e6e6065b81227bb878a5ea3714d250354cfa 4.713052373000 1077822 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": 638233, "vin": [ { "gen": { "height": 638223 } } ], "vout": [ { "amount": 4713052373, "target": { "key": "e91c9768378e6b48a4ed80e8dc33e6e6065b81227bb878a5ea3714d250354cfa" } } ], "extra": [ 1, 169, 60, 112, 43, 119, 59, 169, 199, 166, 72, 119, 171, 62, 51, 205, 200, 64, 221, 121, 186, 213, 169, 98, 70, 41, 131, 12, 250, 137, 17, 167, 119, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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