Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e4e7d87a151cde51053fbe993bb932072b0992ef12d66fa7b50b3868db42e0

Tx prefix hash: bb9cdbd9cbafefccdf77822625647d6468f084a740036ed65847fb80c37589e8
Tx public key: 8d4533e94bccae877e63e309dbbb59e68e35cf6a0f4dc94b1cd8b00292129ad9
Timestamp: 1581427352 Timestamp [UCT]: 2020-02-11 13:22:32 Age [y:d:h:m:s]: 05:267:13:21:03
Block: 62605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1341887 RingCT/type: yes/0
Extra: 018d4533e94bccae877e63e309dbbb59e68e35cf6a0f4dc94b1cd8b00292129ad9021100000005c71d3ff9000000000000000000

1 output(s) for total of 380.683857097000 dcy

stealth address amount amount idx
00: 42a79254b0f4ec6caa8d8bd23b269f63976e5219e678ca9561aee70dc9346b5b 380.683857097000 115571 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": 62615, "vin": [ { "gen": { "height": 62605 } } ], "vout": [ { "amount": 380683857097, "target": { "key": "42a79254b0f4ec6caa8d8bd23b269f63976e5219e678ca9561aee70dc9346b5b" } } ], "extra": [ 1, 141, 69, 51, 233, 75, 204, 174, 135, 126, 99, 227, 9, 219, 187, 89, 230, 142, 53, 207, 106, 15, 77, 201, 75, 28, 216, 176, 2, 146, 18, 154, 217, 2, 17, 0, 0, 0, 5, 199, 29, 63, 249, 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