Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cd0684b4ef8e7287c516315d9cdffef5fa537a441ab98ae8093c56312f22d6

Tx prefix hash: 388c20eb72f8c8973e6177603afa2f135cc59bc0c675ce4a4358c7c7e5c6acc5
Tx public key: c8f42782ba20f1b989436e7f9390a4c61ca5a93119502e06aa3be49eaec26c62
Timestamp: 1691071548 Timestamp [UCT]: 2023-08-03 14:05:48 Age [y:d:h:m:s]: 02:179:02:10:12
Block: 817991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647588 RingCT/type: yes/0
Extra: 01c8f42782ba20f1b989436e7f9390a4c61ca5a93119502e06aa3be49eaec26c62021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.205923962000 dcy

stealth address amount amount idx
00: 885b0e10ed8a1ad29e36aac780602b7e6d1097c8d48f14d6dee5cbbc47ea6060 1.205923962000 1269927 of 0

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": 818001, "vin": [ { "gen": { "height": 817991 } } ], "vout": [ { "amount": 1205923962, "target": { "key": "885b0e10ed8a1ad29e36aac780602b7e6d1097c8d48f14d6dee5cbbc47ea6060" } } ], "extra": [ 1, 200, 244, 39, 130, 186, 32, 241, 185, 137, 67, 110, 127, 147, 144, 164, 198, 28, 165, 169, 49, 25, 80, 46, 6, 170, 59, 228, 158, 174, 194, 108, 98, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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