Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 629350fce68258d3b02e670b6489d73063614f715ee368ef4a4a22e7feca93ee

Tx prefix hash: 4c557cc65eb5d371f1bcca4173f2ccd1ca06c0c396872787459ffdffbf70be06
Tx public key: f8d2b505dd3c8fae99b4a27389509bd92c8ebf80fef87bbf83a499e5ca3047c5
Timestamp: 1707179325 Timestamp [UCT]: 2024-02-06 00:28:45 Age [y:d:h:m:s]: 01:360:17:30:47
Block: 951256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516517 RingCT/type: yes/0
Extra: 01f8d2b505dd3c8fae99b4a27389509bd92c8ebf80fef87bbf83a499e5ca3047c50211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 363f051834511d5a607125dede01b78401a702449d57206f4a3587cd0f4ce4da 0.600000000000 1409996 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": 951266, "vin": [ { "gen": { "height": 951256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "363f051834511d5a607125dede01b78401a702449d57206f4a3587cd0f4ce4da" } } ], "extra": [ 1, 248, 210, 181, 5, 221, 60, 143, 174, 153, 180, 162, 115, 137, 80, 155, 217, 44, 142, 191, 128, 254, 248, 123, 191, 131, 164, 153, 229, 202, 48, 71, 197, 2, 17, 0, 0, 0, 5, 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