Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c024a5ba83e8761ad966b180afec2f44d3ce63f2bbe0382d3c6eee74ae85dfe

Tx prefix hash: 4cee8c40c5b6270f6be4a9c8a7c847535dc2734552208a4f0d592bc55b4f1b32
Tx public key: b0a6731531aa3abe650dd34f464af8f3fbd96e878390fb1a59f0a5aad7930492
Timestamp: 1763777743 Timestamp [UCT]: 2025-11-22 02:15:43 Age [y:d:h:m:s]: 00:031:01:21:23
Block: 1417359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22245 RingCT/type: yes/0
Extra: 01b0a6731531aa3abe650dd34f464af8f3fbd96e878390fb1a59f0a5aad7930492021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 797d38a09a847f3942b24bcd5936d9be8ea5b322551f807fd30fdabc0717ec03 0.600000000000 1905882 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": 1417369, "vin": [ { "gen": { "height": 1417359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "797d38a09a847f3942b24bcd5936d9be8ea5b322551f807fd30fdabc0717ec03" } } ], "extra": [ 1, 176, 166, 115, 21, 49, 170, 58, 190, 101, 13, 211, 79, 70, 74, 248, 243, 251, 217, 110, 135, 131, 144, 251, 26, 89, 240, 165, 170, 215, 147, 4, 146, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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