Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0a80e8ac1dc62e205b95b5bd6715c46d4f7000f1181286591dc87a9dc68ddb

Tx prefix hash: 5dc97c8189323107dc35945c176b0a8895e950361e7136fcfa1c66308f10fa4b
Tx public key: edb44c230246fae7a8151fe8dbd22488366f7e654ca538efb1094f5b8f2a5768
Timestamp: 1716328111 Timestamp [UCT]: 2024-05-21 21:48:31 Age [y:d:h:m:s]: 00:282:05:01:15
Block: 1027117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201682 RingCT/type: yes/0
Extra: 01edb44c230246fae7a8151fe8dbd22488366f7e654ca538efb1094f5b8f2a57680211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 670d59dd1c2ea3d99cacca0a9c27dc928bb5cc32e444303f0fa99915ee7d3aea 0.600000000000 1494572 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": 1027127, "vin": [ { "gen": { "height": 1027117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "670d59dd1c2ea3d99cacca0a9c27dc928bb5cc32e444303f0fa99915ee7d3aea" } } ], "extra": [ 1, 237, 180, 76, 35, 2, 70, 250, 231, 168, 21, 31, 232, 219, 210, 36, 136, 54, 111, 126, 101, 76, 165, 56, 239, 177, 9, 79, 91, 143, 42, 87, 104, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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