Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2d82e2309465dae5e6176e5718027c7db1bccee33443d6bb2fa691209ef72a

Tx prefix hash: e3c0edd2dc0999da5c6e90cd1cb0d0cb31fb3793ad475b247f3a24a405784b1d
Tx public key: e565940bbe7c4ebaf9a38d689689b6c2d487e154ecbd14b9a5fd0bc4db17986e
Timestamp: 1732303794 Timestamp [UCT]: 2024-11-22 19:29:54 Age [y:d:h:m:s]: 00:001:03:04:58
Block: 1159463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806 RingCT/type: yes/0
Extra: 01e565940bbe7c4ebaf9a38d689689b6c2d487e154ecbd14b9a5fd0bc4db17986e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553f14ab9c7c8ce5b33e4fc7b5a4e6326f95235ecfed0a55ec37067af232f5ab 0.600000000000 1645100 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": 1159473, "vin": [ { "gen": { "height": 1159463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553f14ab9c7c8ce5b33e4fc7b5a4e6326f95235ecfed0a55ec37067af232f5ab" } } ], "extra": [ 1, 229, 101, 148, 11, 190, 124, 78, 186, 249, 163, 141, 104, 150, 137, 182, 194, 212, 135, 225, 84, 236, 189, 20, 185, 165, 253, 11, 196, 219, 23, 152, 110, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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