Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42b911fe206342aa72d6390db0d2b5a42b64b63220be7a6eb30ed028fbc3def5

Tx prefix hash: da1f9195d5c887c12c58d9a1a6a324ea31fcad2b8d1102beb5a39dda36a8cca8
Tx public key: 30496bc4b85799dc73423a79c1675b8294d1ded2cd32f9756d319703a63d07f4
Timestamp: 1750291507 Timestamp [UCT]: 2025-06-19 00:05:07 Age [y:d:h:m:s]: 00:154:08:17:56
Block: 1307985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108129 RingCT/type: yes/0
Extra: 0130496bc4b85799dc73423a79c1675b8294d1ded2cd32f9756d319703a63d07f40211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1603b382ae5c7d5e598b2c3262ca0820e4e892ddfb7d9fed2ad86d7002a68df9 0.600000000000 1795596 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": 1307995, "vin": [ { "gen": { "height": 1307985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1603b382ae5c7d5e598b2c3262ca0820e4e892ddfb7d9fed2ad86d7002a68df9" } } ], "extra": [ 1, 48, 73, 107, 196, 184, 87, 153, 220, 115, 66, 58, 121, 193, 103, 91, 130, 148, 209, 222, 210, 205, 50, 249, 117, 109, 49, 151, 3, 166, 61, 7, 244, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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