Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0068c35da17e3066e8839a4d22eb469dae8a81117425947e3b6f352c648e68ea

Tx prefix hash: d7bb81f3f4442b755bdc78f70163573fb77afa998cdd1c092eda6c638c76299c
Tx public key: 8f5ea01ca2726a0764b6d480e148efb47c4f95d6afd13956e1a4b4561bc3ee19
Timestamp: 1710378205 Timestamp [UCT]: 2024-03-14 01:03:25 Age [y:d:h:m:s]: 00:346:16:05:26
Block: 977803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247832 RingCT/type: yes/0
Extra: 018f5ea01ca2726a0764b6d480e148efb47c4f95d6afd13956e1a4b4561bc3ee190211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0435bed29854234c7a18605e4d8205c1c66c1c9d4fc439a137d9e3537f1c35 0.600000000000 1437810 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": 977813, "vin": [ { "gen": { "height": 977803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0435bed29854234c7a18605e4d8205c1c66c1c9d4fc439a137d9e3537f1c35" } } ], "extra": [ 1, 143, 94, 160, 28, 162, 114, 106, 7, 100, 182, 212, 128, 225, 72, 239, 180, 124, 79, 149, 214, 175, 209, 57, 86, 225, 164, 180, 86, 27, 195, 238, 25, 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