Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad53bac84151147e9ea6641eb5bf5c35c871822e1c7129a7fc885efd453eb2a

Tx prefix hash: c57c7893e0a3bfa0c2c2f5500788c10e91d8526635011ca8f7bade75d9a4921e
Tx public key: f20d0b8c01fb60d6929fce8d53f0cf279aa1b8234bf0daca1d6174fb19e22b83
Timestamp: 1758280986 Timestamp [UCT]: 2025-09-19 11:23:06 Age [y:d:h:m:s]: 00:095:12:54:15
Block: 1371818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68389 RingCT/type: yes/0
Extra: 01f20d0b8c01fb60d6929fce8d53f0cf279aa1b8234bf0daca1d6174fb19e22b83021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa7e51dc9bf4bbaa2c525641ba50a09d874277bd4965dd4fa20eca74c49caa45 0.600000000000 1859895 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": 1371828, "vin": [ { "gen": { "height": 1371818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7e51dc9bf4bbaa2c525641ba50a09d874277bd4965dd4fa20eca74c49caa45" } } ], "extra": [ 1, 242, 13, 11, 140, 1, 251, 96, 214, 146, 159, 206, 141, 83, 240, 207, 39, 154, 161, 184, 35, 75, 240, 218, 202, 29, 97, 116, 251, 25, 226, 43, 131, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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