Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d1e69e487f36f4ec7cdb86faa94d7b01d330332089d6808976e00c18f04b2e4

Tx prefix hash: 659d7dca16d692a9cf35c3afa1521699619a8b1baf5aeae23cdab94d338d9de9
Tx public key: a6513ff7e8d82eee68f8fae1e2591253746ee89747d315e55185ab5a137e0b05
Timestamp: 1715661079 Timestamp [UCT]: 2024-05-14 04:31:19 Age [y:d:h:m:s]: 00:242:01:51:24
Block: 1021584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173269 RingCT/type: yes/0
Extra: 01a6513ff7e8d82eee68f8fae1e2591253746ee89747d315e55185ab5a137e0b050211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2e88fff2049738dc589d5b9627a84bdeca6e1b5e291487f0f861c0af009d65 0.600000000000 1485943 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": 1021594, "vin": [ { "gen": { "height": 1021584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2e88fff2049738dc589d5b9627a84bdeca6e1b5e291487f0f861c0af009d65" } } ], "extra": [ 1, 166, 81, 63, 247, 232, 216, 46, 238, 104, 248, 250, 225, 226, 89, 18, 83, 116, 110, 232, 151, 71, 211, 21, 229, 81, 133, 171, 90, 19, 126, 11, 5, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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