Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1785bfa820ffa1f1b2aa720d7401a58010b5cc7417b6d4fac448a4b9ecc38518

Tx prefix hash: be4a350e7fa5a510e39bde971ada3f1988774fdbd2870e6bc41706f4d4f6e3b8
Tx public key: 20f6e1423d5e92e78db5062ea7a7466a70981a058dcaf0c5d87701fa87274b32
Timestamp: 1763952285 Timestamp [UCT]: 2025-11-24 02:44:45 Age [y:d:h:m:s]: 00:003:05:10:12
Block: 1418814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2304 RingCT/type: yes/0
Extra: 0120f6e1423d5e92e78db5062ea7a7466a70981a058dcaf0c5d87701fa87274b320211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d64a0695761d86beb30ed955b6ed5a64cceb0c5fe373a30dc31d4ab9deaafa61 0.600000000000 1907347 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": 1418824, "vin": [ { "gen": { "height": 1418814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d64a0695761d86beb30ed955b6ed5a64cceb0c5fe373a30dc31d4ab9deaafa61" } } ], "extra": [ 1, 32, 246, 225, 66, 61, 94, 146, 231, 141, 181, 6, 46, 167, 167, 70, 106, 112, 152, 26, 5, 141, 202, 240, 197, 216, 119, 1, 250, 135, 39, 75, 50, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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