Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6435792dae1f2d5c9d725ed826da3e8dc62461ec691ce66e8b176ba9d51ffc

Tx prefix hash: 50304bc7f6142f9d6e9a8d0df3d5b6191860f7acb50a149d562c0fdaf360848c
Tx public key: 9503606e35784041e81b658a007decd8d44279ea9ae44c1343b118e65a3d7f07
Timestamp: 1749768634 Timestamp [UCT]: 2025-06-12 22:50:34 Age [y:d:h:m:s]: 00:151:13:44:58
Block: 1303753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106046 RingCT/type: yes/0
Extra: 019503606e35784041e81b658a007decd8d44279ea9ae44c1343b118e65a3d7f07021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84bde28355c00054671412a1c708d3fa695b18a1b093d47f2753e590bdd3f731 0.600000000000 1791336 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": 1303763, "vin": [ { "gen": { "height": 1303753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84bde28355c00054671412a1c708d3fa695b18a1b093d47f2753e590bdd3f731" } } ], "extra": [ 1, 149, 3, 96, 110, 53, 120, 64, 65, 232, 27, 101, 138, 0, 125, 236, 216, 212, 66, 121, 234, 154, 228, 76, 19, 67, 177, 24, 230, 90, 61, 127, 7, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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