Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8209658ade8f00b2dd78032fbedd037da8c2e23bdf5b21c0518d1ff4d7be7d

Tx prefix hash: cdc210401ffb14d0e30839716d65449b17a8442e018965b3920f102c46baf389
Tx public key: 8fe1b558c73c376f2a66110e6053f462aad02c36d78a29d9d907b5f2be8fe6ab
Timestamp: 1725765684 Timestamp [UCT]: 2024-09-08 03:21:24 Age [y:d:h:m:s]: 01:061:10:36:46
Block: 1105360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302331 RingCT/type: yes/0
Extra: 018fe1b558c73c376f2a66110e6053f462aad02c36d78a29d9d907b5f2be8fe6ab02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ae0cb07b9c849ff9c28e5834dd3eb0996a1295dfad14a49cd9ceeb449f838a 0.600000000000 1582701 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": 1105370, "vin": [ { "gen": { "height": 1105360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ae0cb07b9c849ff9c28e5834dd3eb0996a1295dfad14a49cd9ceeb449f838a" } } ], "extra": [ 1, 143, 225, 181, 88, 199, 60, 55, 111, 42, 102, 17, 14, 96, 83, 244, 98, 170, 208, 44, 54, 215, 138, 41, 217, 217, 7, 181, 242, 190, 143, 230, 171, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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