Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce665fe059da05cd26c14164fb5d1ded1dc8283b26030a37152d943903d89a1

Tx prefix hash: 50326bea106beb8dadfe07493796feaa7619893e8aa81608a5493bcbba1e8b3e
Tx public key: 8d4e9ffc47be8a3a37b50c741124c1480549a9e08b58d3bf05d9f59a8965dc49
Timestamp: 1717892533 Timestamp [UCT]: 2024-06-09 00:22:13 Age [y:d:h:m:s]: 00:322:18:39:14
Block: 1040079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230696 RingCT/type: yes/0
Extra: 018d4e9ffc47be8a3a37b50c741124c1480549a9e08b58d3bf05d9f59a8965dc49021100000003d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1840cd0d56491836e34bd457a612d209c2eae01cc5ceef8a8db5a092ed439cea 0.600000000000 1508734 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": 1040089, "vin": [ { "gen": { "height": 1040079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1840cd0d56491836e34bd457a612d209c2eae01cc5ceef8a8db5a092ed439cea" } } ], "extra": [ 1, 141, 78, 159, 252, 71, 190, 138, 58, 55, 181, 12, 116, 17, 36, 193, 72, 5, 73, 169, 224, 139, 88, 211, 191, 5, 217, 245, 154, 137, 101, 220, 73, 2, 17, 0, 0, 0, 3, 215, 73, 245, 17, 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