Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c628e375c0b5ab250b8802f76305d9d2ed941e6db73d991b1cbdf57614f4cc

Tx prefix hash: 385e5a431e7c8f777a2b7e51c06b0d3fa79fc07ad350201e6201755502c5970f
Tx public key: c7ce49408d4332b9d5ff40bd72a342de652295c7d0baeeffc9a7f188aa7dad49
Timestamp: 1763534306 Timestamp [UCT]: 2025-11-19 06:38:26 Age [y:d:h:m:s]: 00:050:07:52:14
Block: 1415349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36045 RingCT/type: yes/0
Extra: 01c7ce49408d4332b9d5ff40bd72a342de652295c7d0baeeffc9a7f188aa7dad49021100000008defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5c36ebd41a30582b7e0a3543fdeaf86792ae3df3607d2a1cb2db5ab82481a0 0.600000000000 1903850 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": 1415359, "vin": [ { "gen": { "height": 1415349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5c36ebd41a30582b7e0a3543fdeaf86792ae3df3607d2a1cb2db5ab82481a0" } } ], "extra": [ 1, 199, 206, 73, 64, 141, 67, 50, 185, 213, 255, 64, 189, 114, 163, 66, 222, 101, 34, 149, 199, 208, 186, 238, 255, 201, 167, 241, 136, 170, 125, 173, 73, 2, 17, 0, 0, 0, 8, 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