Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d8864daccdcdd528a7308ae9e15c717bae7c294c407c6be3918873dd9cd2757

Tx prefix hash: 27021ede502307131ff29cd633c14e222f513c65afd7fa853a6d808c7dc91208
Tx public key: 6e65da16bd1d493ed1d18d80ab66cebee5971724ead51bd90704d1b5da5ac7b9
Timestamp: 1715054660 Timestamp [UCT]: 2024-05-07 04:04:20 Age [y:d:h:m:s]: 01:038:00:21:58
Block: 1016561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288034 RingCT/type: yes/0
Extra: 016e65da16bd1d493ed1d18d80ab66cebee5971724ead51bd90704d1b5da5ac7b90211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60888c36008a276d7a25832779e1cd7ea63ab8dd9f44a3a07becdc93f659782b 0.600000000000 1480178 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": 1016571, "vin": [ { "gen": { "height": 1016561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60888c36008a276d7a25832779e1cd7ea63ab8dd9f44a3a07becdc93f659782b" } } ], "extra": [ 1, 110, 101, 218, 22, 189, 29, 73, 62, 209, 209, 141, 128, 171, 102, 206, 190, 229, 151, 23, 36, 234, 213, 27, 217, 7, 4, 209, 181, 218, 90, 199, 185, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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