Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7862010e2727ed45031545d29c2405fd8ef42ac87423040db2dbf7c963b587bf

Tx prefix hash: 8e6b23bdc7f37e0cb5e7431719bf10724a3fdd84903ed9d1bb7d56e2607f6789
Tx public key: 62c8ece1e616c66aae86a4be0b19e696db498b6c4be8ae20f40443c743259e86
Timestamp: 1636695695 Timestamp [UCT]: 2021-11-12 05:41:35 Age [y:d:h:m:s]: 03:203:17:10:44
Block: 372600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924048 RingCT/type: yes/0
Extra: 0162c8ece1e616c66aae86a4be0b19e696db498b6c4be8ae20f40443c743259e86021100000001f56b629f000000000000000000

1 output(s) for total of 35.762009718000 dcy

stealth address amount amount idx
00: f2145d7df69641bd416bf58f010d933b7b10fbf60441811f6ce59765ce9afa2d 35.762009718000 754734 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": 372610, "vin": [ { "gen": { "height": 372600 } } ], "vout": [ { "amount": 35762009718, "target": { "key": "f2145d7df69641bd416bf58f010d933b7b10fbf60441811f6ce59765ce9afa2d" } } ], "extra": [ 1, 98, 200, 236, 225, 230, 22, 198, 106, 174, 134, 164, 190, 11, 25, 230, 150, 219, 73, 139, 108, 75, 232, 174, 32, 244, 4, 67, 199, 67, 37, 158, 134, 2, 17, 0, 0, 0, 1, 245, 107, 98, 159, 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