Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72569d6c1f1509acf16e24259b5685c84c48e617248a908a510e92ab411d7c6a

Tx prefix hash: 773e7695856f291254b887a527adcf34f644049d355ee2991e3ba966e3421fcd
Tx public key: 429b24e912d54f62dfcdd0281996ecea7b152e7bcb0a1c19f0981c8397d909e9
Timestamp: 1703265377 Timestamp [UCT]: 2023-12-22 17:16:17 Age [y:d:h:m:s]: 01:181:17:19:07
Block: 918817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390874 RingCT/type: yes/0
Extra: 01429b24e912d54f62dfcdd0281996ecea7b152e7bcb0a1c19f0981c8397d909e902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 645fce4c519c3123202aed7e43c1088d186142c1c000ffdbdfd57ebd6738ba29 0.600000000000 1376481 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": 918827, "vin": [ { "gen": { "height": 918817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "645fce4c519c3123202aed7e43c1088d186142c1c000ffdbdfd57ebd6738ba29" } } ], "extra": [ 1, 66, 155, 36, 233, 18, 213, 79, 98, 223, 205, 208, 40, 25, 150, 236, 234, 123, 21, 46, 123, 203, 10, 28, 25, 240, 152, 28, 131, 151, 217, 9, 233, 2, 17, 0, 0, 0, 7, 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