Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b820295d4d671449b573e34d7614da44fc5d94b5ee217eba9d18212070070a3f

Tx prefix hash: 95c13d5282313559a0075c761a09b3f5fb8d15fe9346137abed4d4fcd3f53b14
Tx public key: e2dee60a000f3244b490fa219a68b2dbf2aff4b501693bd45d6651226fdc57d6
Timestamp: 1720053166 Timestamp [UCT]: 2024-07-04 00:32:46 Age [y:d:h:m:s]: 00:172:04:50:58
Block: 1057986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123269 RingCT/type: yes/0
Extra: 01e2dee60a000f3244b490fa219a68b2dbf2aff4b501693bd45d6651226fdc57d60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee671832d40c725a160a2752ec49b6a0ed72856ff6b5790c4af58a288d6b249 0.600000000000 1528429 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": 1057996, "vin": [ { "gen": { "height": 1057986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee671832d40c725a160a2752ec49b6a0ed72856ff6b5790c4af58a288d6b249" } } ], "extra": [ 1, 226, 222, 230, 10, 0, 15, 50, 68, 180, 144, 250, 33, 154, 104, 178, 219, 242, 175, 244, 181, 1, 105, 59, 212, 93, 102, 81, 34, 111, 220, 87, 214, 2, 17, 0, 0, 0, 2, 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