Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87743889ca36c29607c6ab66888090e5cbe05e2192c4bfef2f3f5593dbdd775

Tx prefix hash: 00b8cddf9acc84c306c9a9afc0c6a07ce6f5e1738524dd706bce4c2aa2f6d3f7
Tx public key: a7cf5f4e9fe0e4eb8cfd91de570665b85ed053f89d90bb6776952d7e156f484e
Timestamp: 1710914309 Timestamp [UCT]: 2024-03-20 05:58:29 Age [y:d:h:m:s]: 01:015:15:46:18
Block: 982248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272144 RingCT/type: yes/0
Extra: 01a7cf5f4e9fe0e4eb8cfd91de570665b85ed053f89d90bb6776952d7e156f484e02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d8945016edfc5474f5475dba58636ab41c7e8f56f8c23244f4ca634eaca61b6 0.600000000000 1442353 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": 982258, "vin": [ { "gen": { "height": 982248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d8945016edfc5474f5475dba58636ab41c7e8f56f8c23244f4ca634eaca61b6" } } ], "extra": [ 1, 167, 207, 95, 78, 159, 224, 228, 235, 140, 253, 145, 222, 87, 6, 101, 184, 94, 208, 83, 248, 157, 144, 187, 103, 118, 149, 45, 126, 21, 111, 72, 78, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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