Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce402168323da18adfdca78feb3f9d1b7c03c3acaa5c4c4985ce9ddc2d2a8e4e

Tx prefix hash: 5e850097f28cad7f4933d19b88858e2ae2918490b11cb57a0d13da4c51d87b86
Tx public key: 53cdfa4e41e39603ee136e77b0e04f3e8e053904cb084adf25989b509f4a9c00
Timestamp: 1710715690 Timestamp [UCT]: 2024-03-17 22:48:10 Age [y:d:h:m:s]: 00:342:08:23:25
Block: 980606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244725 RingCT/type: yes/0
Extra: 0153cdfa4e41e39603ee136e77b0e04f3e8e053904cb084adf25989b509f4a9c0002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06d1e5b529c9078b8974f264f3f328f7e76a73239894b790b845adce5d61b993 0.600000000000 1440685 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": 980616, "vin": [ { "gen": { "height": 980606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06d1e5b529c9078b8974f264f3f328f7e76a73239894b790b845adce5d61b993" } } ], "extra": [ 1, 83, 205, 250, 78, 65, 227, 150, 3, 238, 19, 110, 119, 176, 224, 79, 62, 142, 5, 57, 4, 203, 8, 74, 223, 37, 152, 155, 80, 159, 74, 156, 0, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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