Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca18f060f61f7bc2918de8d801c4ee1a9dffb4c9c1493b26c5b82ceb430b2dd

Tx prefix hash: 652852daa34c078f66903b0860314556abab33a4edb9a495fd22a1c15e495684
Tx public key: 87b6dbf07e6e2774f10e2064faa859e824d3dd6a2487ae69dfcd79c0973dfe55
Timestamp: 1698482387 Timestamp [UCT]: 2023-10-28 08:39:47 Age [y:d:h:m:s]: 01:160:05:19:08
Block: 879391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375490 RingCT/type: yes/0
Extra: 0187b6dbf07e6e2774f10e2064faa859e824d3dd6a2487ae69dfcd79c0973dfe550211000000074b8f5122000000000000000000

1 output(s) for total of 0.748535803000 dcy

stealth address amount amount idx
00: 3eb56129e579ab1b705783ff5e83027671b21c425198a8d39d9b41ea9f243ece 0.748535803000 1334903 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": 879401, "vin": [ { "gen": { "height": 879391 } } ], "vout": [ { "amount": 748535803, "target": { "key": "3eb56129e579ab1b705783ff5e83027671b21c425198a8d39d9b41ea9f243ece" } } ], "extra": [ 1, 135, 182, 219, 240, 126, 110, 39, 116, 241, 14, 32, 100, 250, 168, 89, 232, 36, 211, 221, 106, 36, 135, 174, 105, 223, 205, 121, 192, 151, 61, 254, 85, 2, 17, 0, 0, 0, 7, 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