Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce6a7f43c26589a95bbdab3f506348a90914d2bf0969e5b0bf51a5865de3cc5

Tx prefix hash: 7707aa289257cf8f020941c2ec6244ebd0b1b244b7637a43d958dad9c5328387
Tx public key: b6284e11f6369a79377607226924b0ca0101b4a5cafa33f62466aa2e99d9c791
Timestamp: 1729844223 Timestamp [UCT]: 2024-10-25 08:17:03 Age [y:d:h:m:s]: 00:029:23:17:03
Block: 1139128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21413 RingCT/type: yes/0
Extra: 01b6284e11f6369a79377607226924b0ca0101b4a5cafa33f62466aa2e99d9c7910211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 993f4e9a448be76cb5e6abf8aa5e79ec7f853791992a3a4ece6c6050d0fa70cb 0.600000000000 1622893 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": 1139138, "vin": [ { "gen": { "height": 1139128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "993f4e9a448be76cb5e6abf8aa5e79ec7f853791992a3a4ece6c6050d0fa70cb" } } ], "extra": [ 1, 182, 40, 78, 17, 246, 54, 154, 121, 55, 118, 7, 34, 105, 36, 176, 202, 1, 1, 180, 165, 202, 250, 51, 246, 36, 102, 170, 46, 153, 217, 199, 145, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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