Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da76fd426cf57a40ebf7024db01301f7114509bfd40edbd270ed1c03323d1a6c

Tx prefix hash: 3c2edecf6032268b69e62814d73b75e8deef6597b25c9079a0e08cda0463ee43
Tx public key: 0a61cde78219f71e94d88c4c33e3eec76075f404fdca4df61d17d3928cccbf92
Timestamp: 1727481829 Timestamp [UCT]: 2024-09-28 00:03:49 Age [y:d:h:m:s]: 00:057:06:01:17
Block: 1119581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40910 RingCT/type: yes/0
Extra: 010a61cde78219f71e94d88c4c33e3eec76075f404fdca4df61d17d3928cccbf9202110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c632dd5685bb7eca2b257c44eb740c345a141876a0e379e37c751c34acc0e0fa 0.600000000000 1601190 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": 1119591, "vin": [ { "gen": { "height": 1119581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c632dd5685bb7eca2b257c44eb740c345a141876a0e379e37c751c34acc0e0fa" } } ], "extra": [ 1, 10, 97, 205, 231, 130, 25, 247, 30, 148, 216, 140, 76, 51, 227, 238, 199, 96, 117, 244, 4, 253, 202, 77, 246, 29, 23, 211, 146, 140, 204, 191, 146, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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