Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c10749704943d3f9f8ac5300175c1e0a4a0b649933cb1493ef4ce6913fe05f

Tx prefix hash: 0303727cd78ebd8aceb52f12b9e16cc5558d93ce4d5f074c484d6f0499c58bb5
Tx public key: f6cb066183c6c51515e0ef05c36b8f727432ed6ca54a1c530bbf4d3867b9b3e1
Timestamp: 1716499646 Timestamp [UCT]: 2024-05-23 21:27:26 Age [y:d:h:m:s]: 01:181:22:26:55
Block: 1028542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388634 RingCT/type: yes/0
Extra: 01f6cb066183c6c51515e0ef05c36b8f727432ed6ca54a1c530bbf4d3867b9b3e10211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 295d91e53aa164cb00e9ab02f53c023c60175818330c73097bfde9f2664e2ee4 0.600000000000 1496535 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": 1028552, "vin": [ { "gen": { "height": 1028542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "295d91e53aa164cb00e9ab02f53c023c60175818330c73097bfde9f2664e2ee4" } } ], "extra": [ 1, 246, 203, 6, 97, 131, 198, 197, 21, 21, 224, 239, 5, 195, 107, 143, 114, 116, 50, 237, 108, 165, 74, 28, 83, 11, 191, 77, 56, 103, 185, 179, 225, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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