Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c66616fe91b1a0ea881f1a1593a529fb27a0c9e5304f20fc4687fe5719378fc

Tx prefix hash: 546ada711776672d8730d76b6e80780bd79e36d37d893025fa6a24870e6a007e
Tx public key: 1e8a0f070440e520f1ddaba7d21e3f9cb2ec3ea5d50a5ad388d6d73ace912127
Timestamp: 1751643074 Timestamp [UCT]: 2025-07-04 15:31:14 Age [y:d:h:m:s]: 00:132:19:14:27
Block: 1318690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93203 RingCT/type: yes/0
Extra: 011e8a0f070440e520f1ddaba7d21e3f9cb2ec3ea5d50a5ad388d6d73ace912127021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65783725d41b6053d0f929e3f4d6b31918e60cabe0df7751a09f8b6fe20631b9 0.600000000000 1806375 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": 1318700, "vin": [ { "gen": { "height": 1318690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65783725d41b6053d0f929e3f4d6b31918e60cabe0df7751a09f8b6fe20631b9" } } ], "extra": [ 1, 30, 138, 15, 7, 4, 64, 229, 32, 241, 221, 171, 167, 210, 30, 63, 156, 178, 236, 62, 165, 213, 10, 90, 211, 136, 214, 215, 58, 206, 145, 33, 39, 2, 17, 0, 0, 0, 1, 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