Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77af0e3bee1a96a16f415b258d27ead05683f2741d410e0106bff28eae6f9521

Tx prefix hash: f52b283ac57cfcd82ba074439cc13884e05037f478a5d504acca3d649e0d079a
Tx public key: 65e79e0bd55654e8e5d1c749d5bf60b7dd4e8423f72252eb12f4f19ffe7408ce
Timestamp: 1763075899 Timestamp [UCT]: 2025-11-13 23:18:19 Age [y:d:h:m:s]: 00:055:18:09:00
Block: 1411553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39925 RingCT/type: yes/0
Extra: 0165e79e0bd55654e8e5d1c749d5bf60b7dd4e8423f72252eb12f4f19ffe7408ce021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 297fc5302b5c19332aeef06a1c358f3f7fb7483be9a7ebed4aa02c39107e6bd3 0.600000000000 1900016 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": 1411563, "vin": [ { "gen": { "height": 1411553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "297fc5302b5c19332aeef06a1c358f3f7fb7483be9a7ebed4aa02c39107e6bd3" } } ], "extra": [ 1, 101, 231, 158, 11, 213, 86, 84, 232, 229, 209, 199, 73, 213, 191, 96, 183, 221, 78, 132, 35, 247, 34, 82, 235, 18, 244, 241, 159, 254, 116, 8, 206, 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