Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed366a10d5d79bd797327496232c35dbf1aea9b6550eb313408feff9b39435c1

Tx prefix hash: caa91b251d34c71dc24d210b59c98fd076dc73d65ab3ff1073b6b42220fb3128
Tx public key: cc419247a16d9b3e98748d3141e858fd78ecec6c8a50acc8b31ec922d62df666
Timestamp: 1763371636 Timestamp [UCT]: 2025-11-17 09:27:16 Age [y:d:h:m:s]: 00:051:02:23:05
Block: 1413998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36594 RingCT/type: yes/0
Extra: 01cc419247a16d9b3e98748d3141e858fd78ecec6c8a50acc8b31ec922d62df666021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6a27d87c5f9dad1adc46eeb2640f2ff62d4a1c7f905fbfa620a46dc70d5593 0.600000000000 1902483 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": 1414008, "vin": [ { "gen": { "height": 1413998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6a27d87c5f9dad1adc46eeb2640f2ff62d4a1c7f905fbfa620a46dc70d5593" } } ], "extra": [ 1, 204, 65, 146, 71, 161, 109, 155, 62, 152, 116, 141, 49, 65, 232, 88, 253, 120, 236, 236, 108, 138, 80, 172, 200, 179, 30, 201, 34, 214, 45, 246, 102, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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