Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7e7378d658565e46f87bdf8dc3ec4d68c9ad8f5f7df67b08fa2cdd125e4397a

Tx prefix hash: 33160c43e4fe784fa15c254c6df22d5aa0df0d782be3637b93a737bcca4999ee
Tx public key: 75ba28b6a08d7729598b205d4ae9417d3a93818609056c903631d04b84ebda08
Timestamp: 1763281017 Timestamp [UCT]: 2025-11-16 08:16:57 Age [y:d:h:m:s]: 00:048:04:34:14
Block: 1413249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34509 RingCT/type: yes/0
Extra: 0175ba28b6a08d7729598b205d4ae9417d3a93818609056c903631d04b84ebda08021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e01e6f67c800910b799cf37c08a74cf912a5ab73235118fcf7eea5c8f8ae484f 0.600000000000 1901726 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": 1413259, "vin": [ { "gen": { "height": 1413249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e01e6f67c800910b799cf37c08a74cf912a5ab73235118fcf7eea5c8f8ae484f" } } ], "extra": [ 1, 117, 186, 40, 182, 160, 141, 119, 41, 89, 139, 32, 93, 74, 233, 65, 125, 58, 147, 129, 134, 9, 5, 108, 144, 54, 49, 208, 75, 132, 235, 218, 8, 2, 17, 0, 0, 0, 3, 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