Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d76da612b86e089edfbe55c7cf4425e62cdf4f5041b4578b540f1efca4e3ade

Tx prefix hash: 5a886732c473913c8255360339b09d6f7cbe76ebc4b67f579ebc18caa93f9694
Tx public key: 28e643b5794ac7f3abb8d37125a84712b057bc7c18a8c466551fcaa1ae188e2a
Timestamp: 1763109887 Timestamp [UCT]: 2025-11-14 08:44:47 Age [y:d:h:m:s]: 00:039:01:54:20
Block: 1411834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27963 RingCT/type: yes/0
Extra: 0128e643b5794ac7f3abb8d37125a84712b057bc7c18a8c466551fcaa1ae188e2a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2ab0bc64627f5635b32640ae79ea7afef94be79717122fc706d6810e3c5c064 0.600000000000 1900299 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": 1411844, "vin": [ { "gen": { "height": 1411834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2ab0bc64627f5635b32640ae79ea7afef94be79717122fc706d6810e3c5c064" } } ], "extra": [ 1, 40, 230, 67, 181, 121, 74, 199, 243, 171, 184, 211, 113, 37, 168, 71, 18, 176, 87, 188, 124, 24, 168, 196, 102, 85, 31, 202, 161, 174, 24, 142, 42, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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