Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06475d0478d30634ac2f4fe2f259066fa86796cf4ef4023759827dfa85cb0c80

Tx prefix hash: 491fb6bc01d8e9ceb7217fbf27534a9ad78e8a12f05b260c357d7277a37c8f9b
Tx public key: 63375fae9b5fc2ab7b91685f67888dac0f538c053bb9a57098d797a9689f36f8
Timestamp: 1705328721 Timestamp [UCT]: 2024-01-15 14:25:21 Age [y:d:h:m:s]: 01:294:16:18:48
Block: 935906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469415 RingCT/type: yes/0
Extra: 0163375fae9b5fc2ab7b91685f67888dac0f538c053bb9a57098d797a9689f36f80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0cf9b67efdc7b9f28b99f0b7492fa7d43591434c33716b87b28ff42f359d704 0.600000000000 1393924 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": 935916, "vin": [ { "gen": { "height": 935906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0cf9b67efdc7b9f28b99f0b7492fa7d43591434c33716b87b28ff42f359d704" } } ], "extra": [ 1, 99, 55, 95, 174, 155, 95, 194, 171, 123, 145, 104, 95, 103, 136, 141, 172, 15, 83, 140, 5, 59, 185, 165, 112, 152, 215, 151, 169, 104, 159, 54, 248, 2, 17, 0, 0, 0, 1, 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