Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac666952a87b284987e1a9defc4ac0ee109d18bd3f0fe0dae79d066424d05f1a

Tx prefix hash: b47390e828b1c25af8777d42ad8c5c18e3a5f8db4140d1da2fed82194a1ea972
Tx public key: 6dcbec390b7a191bc542e2886b0fb4c1e962a08058e73aa06d0abb41f99e7017
Timestamp: 1765030443 Timestamp [UCT]: 2025-12-06 14:14:03 Age [y:d:h:m:s]: 00:017:08:32:26
Block: 1427745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12419 RingCT/type: yes/0
Extra: 016dcbec390b7a191bc542e2886b0fb4c1e962a08058e73aa06d0abb41f99e7017021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40989cf49856cce6fcedcf6528bb0ec35d17aa1b99313347a6ecdae922226a65 0.600000000000 1916450 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": 1427755, "vin": [ { "gen": { "height": 1427745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40989cf49856cce6fcedcf6528bb0ec35d17aa1b99313347a6ecdae922226a65" } } ], "extra": [ 1, 109, 203, 236, 57, 11, 122, 25, 27, 197, 66, 226, 136, 107, 15, 180, 193, 233, 98, 160, 128, 88, 231, 58, 160, 109, 10, 187, 65, 249, 158, 112, 23, 2, 17, 0, 0, 0, 7, 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