Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcdaad42062cb3a100afc266c073638440bcfc6f4fbe3b97af6f3cbc42cb53a1

Tx prefix hash: a70910c18d1d70c9ce0aeb2125fb2caadeb4caaecc79ff13142893f8386fd089
Tx public key: a6013605b1c0b16c5fcde952663e6832a27c35c77ae8b2364b10d9fc53ace992
Timestamp: 1695003713 Timestamp [UCT]: 2023-09-18 02:21:53 Age [y:d:h:m:s]: 01:163:17:37:02
Block: 850511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378078 RingCT/type: yes/0
Extra: 01a6013605b1c0b16c5fcde952663e6832a27c35c77ae8b2364b10d9fc53ace9920211000000074b8f5122000000000000000000

1 output(s) for total of 0.933048135000 dcy

stealth address amount amount idx
00: c750543e9fe0bb0d857e384924bfbff7b69218cced41dfac8f42891fac368040 0.933048135000 1304233 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": 850521, "vin": [ { "gen": { "height": 850511 } } ], "vout": [ { "amount": 933048135, "target": { "key": "c750543e9fe0bb0d857e384924bfbff7b69218cced41dfac8f42891fac368040" } } ], "extra": [ 1, 166, 1, 54, 5, 177, 192, 177, 108, 95, 205, 233, 82, 102, 62, 104, 50, 162, 124, 53, 199, 122, 232, 178, 54, 75, 16, 217, 252, 83, 172, 233, 146, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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