Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddcba6328e152cf3276fd3a061749e37c7fa16ef9358ad8d62e86725e71af59a

Tx prefix hash: 7d263e208f1a180551a99ba76c8d9ea6bc5b0f4574bc991862a1ab751f1a8453
Tx public key: bcf6dd935f82ef5daf5d052e961a3ec41ac6351aff30bb7affd5b07809d6ba18
Timestamp: 1757900563 Timestamp [UCT]: 2025-09-15 01:42:43 Age [y:d:h:m:s]: 00:100:00:40:15
Block: 1368661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71609 RingCT/type: yes/0
Extra: 01bcf6dd935f82ef5daf5d052e961a3ec41ac6351aff30bb7affd5b07809d6ba18021100000008b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db4b899efad4752e870f9686241e62b659c810e0dcafbf08f2be783f3ebe8a3e 0.600000000000 1856712 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": 1368671, "vin": [ { "gen": { "height": 1368661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db4b899efad4752e870f9686241e62b659c810e0dcafbf08f2be783f3ebe8a3e" } } ], "extra": [ 1, 188, 246, 221, 147, 95, 130, 239, 93, 175, 93, 5, 46, 150, 26, 62, 196, 26, 198, 53, 26, 255, 48, 187, 122, 255, 213, 176, 120, 9, 214, 186, 24, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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