Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd511e685bfa0e06129cc0f6821e73574ccdc72f1991e58aa163444525b01ea

Tx prefix hash: 69feb45c21d623b63cf582679c6295e0765a65ca25730c5c60e9faee6e4c765a
Tx public key: 4fa7d08ab2241c2dbe7f3da244acdbe8472b8351ae5933ee4665a62a537b0f7f
Timestamp: 1763446563 Timestamp [UCT]: 2025-11-18 06:16:03 Age [y:d:h:m:s]: 00:050:04:31:40
Block: 1414617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35941 RingCT/type: yes/0
Extra: 014fa7d08ab2241c2dbe7f3da244acdbe8472b8351ae5933ee4665a62a537b0f7f02110000000243b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e94b2ca9b107059f473854fb056bbb4aa67fe1748c92dfd639324e6b54ece407 0.600000000000 1903108 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": 1414627, "vin": [ { "gen": { "height": 1414617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e94b2ca9b107059f473854fb056bbb4aa67fe1748c92dfd639324e6b54ece407" } } ], "extra": [ 1, 79, 167, 208, 138, 178, 36, 28, 45, 190, 127, 61, 162, 68, 172, 219, 232, 71, 43, 131, 81, 174, 89, 51, 238, 70, 101, 166, 42, 83, 123, 15, 127, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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