Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 217b32764d984d3be5939f92012fe0d67e3b162f0f762562a700b082f04636ec

Tx prefix hash: bd708d2080a5997f96f56c0ee0262ac702d196f78367546f9179715a43d607bc
Tx public key: ca8ccb1db4cf2da5eed80e73f3c0fb59781f6c2de552c9bd7a772fe5d9bcd37b
Timestamp: 1759889384 Timestamp [UCT]: 2025-10-08 02:09:44 Age [y:d:h:m:s]: 00:033:05:22:13
Block: 1385129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23807 RingCT/type: yes/0
Extra: 01ca8ccb1db4cf2da5eed80e73f3c0fb59781f6c2de552c9bd7a772fe5d9bcd37b021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee5123539beec87cc979e84f34f8b5eba045bcf1a627b931e5f9ef646190c97e 0.600000000000 1873286 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": 1385139, "vin": [ { "gen": { "height": 1385129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee5123539beec87cc979e84f34f8b5eba045bcf1a627b931e5f9ef646190c97e" } } ], "extra": [ 1, 202, 140, 203, 29, 180, 207, 45, 165, 238, 216, 14, 115, 243, 192, 251, 89, 120, 31, 108, 45, 229, 82, 201, 189, 122, 119, 47, 229, 217, 188, 211, 123, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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