Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1c82f685dfe2219700f34f6196995e223fb055c58d45c04eea53d9e8d3582c

Tx prefix hash: c22ee6c3c82d3b509d86682028122729f852a3ce9627675fda74b64c2cc69cd1
Tx public key: 7b9841d4ed06b621008c9323f8b56fe56a66f71f6cc81a923dd79f8ad6157bcd
Timestamp: 1749557330 Timestamp [UCT]: 2025-06-10 12:08:50 Age [y:d:h:m:s]: 00:156:00:16:00
Block: 1302056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109170 RingCT/type: yes/0
Extra: 017b9841d4ed06b621008c9323f8b56fe56a66f71f6cc81a923dd79f8ad6157bcd021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a412f6fa926f557a309a6383e7ceb53db0da3a5e3415dd9de7e81e10bd189e 0.600000000000 1789625 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": 1302066, "vin": [ { "gen": { "height": 1302056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a412f6fa926f557a309a6383e7ceb53db0da3a5e3415dd9de7e81e10bd189e" } } ], "extra": [ 1, 123, 152, 65, 212, 237, 6, 182, 33, 0, 140, 147, 35, 248, 181, 111, 229, 106, 102, 247, 31, 108, 200, 26, 146, 61, 215, 159, 138, 214, 21, 123, 205, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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