Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbef6539d5e6d09ab48e1e060de97d5e19a767f712799d409291811f7e5147a

Tx prefix hash: ed9aa8e21914f5a2f9301252615c71483e0d48411f5018241700ba57438d5565
Tx public key: 5d7854fcd5c7b8d884dceb87066eeb96ca1da0c84ffcde2b123e43121f5bb11c
Timestamp: 1738618109 Timestamp [UCT]: 2025-02-03 21:28:29 Age [y:d:h:m:s]: 00:290:14:34:56
Block: 1211477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205457 RingCT/type: yes/0
Extra: 015d7854fcd5c7b8d884dceb87066eeb96ca1da0c84ffcde2b123e43121f5bb11c02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2151bafcfc64ba80ec414c8faad0bbf1e09ab711ed04cf822f9d2694043f2f60 0.600000000000 1698238 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": 1211487, "vin": [ { "gen": { "height": 1211477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2151bafcfc64ba80ec414c8faad0bbf1e09ab711ed04cf822f9d2694043f2f60" } } ], "extra": [ 1, 93, 120, 84, 252, 213, 199, 184, 216, 132, 220, 235, 135, 6, 110, 235, 150, 202, 29, 160, 200, 79, 252, 222, 43, 18, 62, 67, 18, 31, 91, 177, 28, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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