Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e674045aaf0c174803f1025d726f9fcb3e4bbc902f9ab87eb650376db733c8a

Tx prefix hash: 7810329f4e5572ec5e9c87afd33b1a33c40809da741552d788a986c322d73f22
Tx public key: 28c9230f6ad40fa5616d7119c7777a6ed5e42fdc6123d217ac0659ca3af7a3a1
Timestamp: 1703410057 Timestamp [UCT]: 2023-12-24 09:27:37 Age [y:d:h:m:s]: 01:066:14:05:10
Block: 920019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308668 RingCT/type: yes/0
Extra: 0128c9230f6ad40fa5616d7119c7777a6ed5e42fdc6123d217ac0659ca3af7a3a102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1033f181f7993af621d882bf7ea2953cc259b5b97071465d9b16596c9e370668 0.600000000000 1377697 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": 920029, "vin": [ { "gen": { "height": 920019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1033f181f7993af621d882bf7ea2953cc259b5b97071465d9b16596c9e370668" } } ], "extra": [ 1, 40, 201, 35, 15, 106, 212, 15, 165, 97, 109, 113, 25, 199, 119, 122, 110, 213, 228, 47, 220, 97, 35, 210, 23, 172, 6, 89, 202, 58, 247, 163, 161, 2, 17, 0, 0, 0, 3, 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