Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ffdc956d825e5d0b40c730a4a59eb8371d3482abbcda237d9c200a5fd7fd61

Tx prefix hash: 1eb676e5a3405a8c86735f2ecc6edfbc0ead81c1f4c43b95cb7d7cded74f024b
Tx public key: 832cd60477c67f1dd83262c43509b05b719f20be17ede872fb40121cf1736237
Timestamp: 1766455961 Timestamp [UCT]: 2025-12-23 02:12:41 Age [y:d:h:m:s]: 00:017:06:14:07
Block: 1439559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12369 RingCT/type: yes/0
Extra: 01832cd60477c67f1dd83262c43509b05b719f20be17ede872fb40121cf1736237021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cac94dd910c63592d9101cd269cff29d3f5e639c7e6b8d2ae02730fbbaa297d 0.600000000000 1928406 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": 1439569, "vin": [ { "gen": { "height": 1439559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cac94dd910c63592d9101cd269cff29d3f5e639c7e6b8d2ae02730fbbaa297d" } } ], "extra": [ 1, 131, 44, 214, 4, 119, 198, 127, 29, 216, 50, 98, 196, 53, 9, 176, 91, 113, 159, 32, 190, 23, 237, 232, 114, 251, 64, 18, 28, 241, 115, 98, 55, 2, 17, 0, 0, 0, 1, 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