Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2a42e24fb57fb79898e3dfe80c6b77dcd1a0ce9dca84bf756bf13e1c992e85

Tx prefix hash: cb5df73e277bc7602ba23574cb5ac258d3923174da611666af028e4b1cdd7558
Tx public key: 575ab41b2215e64ed2048460d90316ee132c7e9651de64e87bfbc61c70da5828
Timestamp: 1724456284 Timestamp [UCT]: 2024-08-23 23:38:04 Age [y:d:h:m:s]: 00:274:19:30:35
Block: 1094509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196304 RingCT/type: yes/0
Extra: 01575ab41b2215e64ed2048460d90316ee132c7e9651de64e87bfbc61c70da5828021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2e105b8cb3aaf759d60f094e2d6b15af06fc50c9e29bd2f9ba964e26612594e 0.600000000000 1569626 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": 1094519, "vin": [ { "gen": { "height": 1094509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2e105b8cb3aaf759d60f094e2d6b15af06fc50c9e29bd2f9ba964e26612594e" } } ], "extra": [ 1, 87, 90, 180, 27, 34, 21, 230, 78, 210, 4, 132, 96, 217, 3, 22, 238, 19, 44, 126, 150, 81, 222, 100, 232, 123, 251, 198, 28, 112, 218, 88, 40, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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