Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a36ab2fc2c11d10e1dbd1e024df11d65eb0da1809b4d567183fcc74c807a32e

Tx prefix hash: 462fcb4e7e3e6b641cfd8268187576b68d60d7e59322972da2cc5275dca6378a
Tx public key: 50384ae957b031cb23b310130aed2c53a59dbdef89de51c368227b32af37c7be
Timestamp: 1684575161 Timestamp [UCT]: 2023-05-20 09:32:41 Age [y:d:h:m:s]: 01:313:16:11:32
Block: 764118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485393 RingCT/type: yes/0
Extra: 0150384ae957b031cb23b310130aed2c53a59dbdef89de51c368227b32af37c7be021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.803682319000 dcy

stealth address amount amount idx
00: 79560f90953012c9ec0fde973ded0ce5088c9c9e7fc9659088923ac9d297c1ef 1.803682319000 1213013 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": 764128, "vin": [ { "gen": { "height": 764118 } } ], "vout": [ { "amount": 1803682319, "target": { "key": "79560f90953012c9ec0fde973ded0ce5088c9c9e7fc9659088923ac9d297c1ef" } } ], "extra": [ 1, 80, 56, 74, 233, 87, 176, 49, 203, 35, 179, 16, 19, 10, 237, 44, 83, 165, 157, 189, 239, 137, 222, 81, 195, 104, 34, 123, 50, 175, 55, 199, 190, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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