Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ace0616d314b7e34279f24aa0ef2e5eb1d2b282a2e936db9c36fb5ea531bc436

Tx prefix hash: 3d31a646d389786e0939bac52ea44504713a1cd9d7e0d8037bf23ce4444cb420
Tx public key: df607a151c3104723bc91b250dbe1f9a7079e8f0c9dc0122ba57cfa62fd651eb
Timestamp: 1695492277 Timestamp [UCT]: 2023-09-23 18:04:37 Age [y:d:h:m:s]: 01:136:06:47:53
Block: 854566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358439 RingCT/type: yes/0
Extra: 01df607a151c3104723bc91b250dbe1f9a7079e8f0c9dc0122ba57cfa62fd651eb0211000000044b8f5122000000000000000000

1 output(s) for total of 0.904624082000 dcy

stealth address amount amount idx
00: 649e14e6ae07a638fc5062319bc38856642199e87257209ddaab31d508c22943 0.904624082000 1308548 of 0

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": 854576, "vin": [ { "gen": { "height": 854566 } } ], "vout": [ { "amount": 904624082, "target": { "key": "649e14e6ae07a638fc5062319bc38856642199e87257209ddaab31d508c22943" } } ], "extra": [ 1, 223, 96, 122, 21, 28, 49, 4, 114, 59, 201, 27, 37, 13, 190, 31, 154, 112, 121, 232, 240, 201, 220, 1, 34, 186, 87, 207, 166, 47, 214, 81, 235, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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