Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8303cc618d0c61f19044d9c9d7f38b3316e9f8526022fef928e77a62a14c455

Tx prefix hash: fc266b5b9400a7d0a0a263871130dec2a6cffce5552ee4af31bb15b14ab635c6
Tx public key: d644aead595b61023443c888a5cea219c291ff37b8fec3ec2ace0940ad2b2b0d
Timestamp: 1764544002 Timestamp [UCT]: 2025-11-30 23:06:42 Age [y:d:h:m:s]: 00:022:10:40:17
Block: 1423722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16061 RingCT/type: yes/0
Extra: 01d644aead595b61023443c888a5cea219c291ff37b8fec3ec2ace0940ad2b2b0d0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9ae9dcab0189830e0e8aa77a86f1798a7f38595d6c6ec529368864608019dcc 0.600000000000 1912343 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": 1423732, "vin": [ { "gen": { "height": 1423722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9ae9dcab0189830e0e8aa77a86f1798a7f38595d6c6ec529368864608019dcc" } } ], "extra": [ 1, 214, 68, 174, 173, 89, 91, 97, 2, 52, 67, 200, 136, 165, 206, 162, 25, 194, 145, 255, 55, 184, 254, 195, 236, 42, 206, 9, 64, 173, 43, 43, 13, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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