Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cef9bc15964c2553e15ccfcf8ffa0b2164e000900dc9ff86b9c8969fad0f74e

Tx prefix hash: f8067f7b48916f436d741347fbcecf6dc753857c7ca3115dfad7fd2f2ebb3176
Tx public key: 1521c74ef303684f88dc66ebbbbd9a5821e850b762e7db3297697c7de2df6f51
Timestamp: 1764057937 Timestamp [UCT]: 2025-11-25 08:05:37 Age [y:d:h:m:s]: 00:001:06:07:50
Block: 1419695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 891 RingCT/type: yes/0
Extra: 011521c74ef303684f88dc66ebbbbd9a5821e850b762e7db3297697c7de2df6f51021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39d1c8b369d6a46c1a06efdfa7859f364fef79174613f59df51034b7aeeeb8f8 0.600000000000 1908234 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": 1419705, "vin": [ { "gen": { "height": 1419695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39d1c8b369d6a46c1a06efdfa7859f364fef79174613f59df51034b7aeeeb8f8" } } ], "extra": [ 1, 21, 33, 199, 78, 243, 3, 104, 79, 136, 220, 102, 235, 187, 189, 154, 88, 33, 232, 80, 183, 98, 231, 219, 50, 151, 105, 124, 125, 226, 223, 111, 81, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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