Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e7da5199dc8147a42d50c0bd905f10802f07ff586255847fbb3535456b2689

Tx prefix hash: 2a2dc6d5c1cab3a038bda186c277acae6c6eb327a8d11603536018ac1d556dfb
Tx public key: bfd4907f54f6c14718c3fb1339d9a1dad10cab152de22ed309c1d853b7df7749
Timestamp: 1750710580 Timestamp [UCT]: 2025-06-23 20:29:40 Age [y:d:h:m:s]: 00:143:09:41:10
Block: 1311346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100410 RingCT/type: yes/0
Extra: 01bfd4907f54f6c14718c3fb1339d9a1dad10cab152de22ed309c1d853b7df774902110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee34ad85b4f7e17e3077df516fe119412be8903342dfe3d3a242223c37687009 0.600000000000 1798973 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": 1311356, "vin": [ { "gen": { "height": 1311346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee34ad85b4f7e17e3077df516fe119412be8903342dfe3d3a242223c37687009" } } ], "extra": [ 1, 191, 212, 144, 127, 84, 246, 193, 71, 24, 195, 251, 19, 57, 217, 161, 218, 209, 12, 171, 21, 45, 226, 46, 211, 9, 193, 216, 83, 183, 223, 119, 73, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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