Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dbe5efb4e111bef73a9f3739609354acb1edc319affd39383e4159e3c80e0bc

Tx prefix hash: d65ee09329606d6ac659bba7ebbd43591c20b5be030be5a66d8fd617642f4b7a
Tx public key: ad636bca1e2d19a9e05781f348f5cdba166a8e2d9ffd5d7ac4ee1278f79f4fec
Timestamp: 1763266606 Timestamp [UCT]: 2025-11-16 04:16:46 Age [y:d:h:m:s]: 00:005:04:08:13
Block: 1413130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3691 RingCT/type: yes/0
Extra: 01ad636bca1e2d19a9e05781f348f5cdba166a8e2d9ffd5d7ac4ee1278f79f4fec021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebd082446d097e2985b943692c4c3a3a5e962d9797861306480947e3805b34d0 0.600000000000 1901607 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": 1413140, "vin": [ { "gen": { "height": 1413130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebd082446d097e2985b943692c4c3a3a5e962d9797861306480947e3805b34d0" } } ], "extra": [ 1, 173, 99, 107, 202, 30, 45, 25, 169, 224, 87, 129, 243, 72, 245, 205, 186, 22, 106, 142, 45, 159, 253, 93, 122, 196, 238, 18, 120, 247, 159, 79, 236, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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