Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae402eecbeb580b87711e36c7ad7fbc15ffe10b9bd74a7bd8eabd47e0e49772d

Tx prefix hash: ff2b14f8f7445efa6c63a0a1f9a38536f3a403b1881a33fea18dbcc71b9a1492
Tx public key: b89ece6a91ab248eafd05ed09be725f2f8a96a90d3f467c50bb2be0507c0ee11
Timestamp: 1713438376 Timestamp [UCT]: 2024-04-18 11:06:16 Age [y:d:h:m:s]: 00:208:23:21:35
Block: 1003137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149618 RingCT/type: yes/0
Extra: 01b89ece6a91ab248eafd05ed09be725f2f8a96a90d3f467c50bb2be0507c0ee110211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce475e55b273c2f9cab79c5496e0b60897429902ae87a092b96f394eff401c5a 0.600000000000 1463667 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": 1003147, "vin": [ { "gen": { "height": 1003137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce475e55b273c2f9cab79c5496e0b60897429902ae87a092b96f394eff401c5a" } } ], "extra": [ 1, 184, 158, 206, 106, 145, 171, 36, 142, 175, 208, 94, 208, 155, 231, 37, 242, 248, 169, 106, 144, 211, 244, 103, 197, 11, 178, 190, 5, 7, 192, 238, 17, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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