Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67777bfff7488a1a3702823f63c23da856c42f40c74fd04f1fb304bfec553d61

Tx prefix hash: dfbd7b422c07a79c9af560958a1a1af5b7185a937affba6933fd16ce6f71e2eb
Tx public key: b9949798f8d4b8bfd6e5a825056d4305a1ff78d144f30c931549a718bfd10027
Timestamp: 1717994873 Timestamp [UCT]: 2024-06-10 04:47:53 Age [y:d:h:m:s]: 00:143:16:44:38
Block: 1040934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102851 RingCT/type: yes/0
Extra: 01b9949798f8d4b8bfd6e5a825056d4305a1ff78d144f30c931549a718bfd100270211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfad9e79a23aed72b53f1d967bc3132bfec751286809299d70aec4fb78dec9b1 0.600000000000 1509599 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": 1040944, "vin": [ { "gen": { "height": 1040934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfad9e79a23aed72b53f1d967bc3132bfec751286809299d70aec4fb78dec9b1" } } ], "extra": [ 1, 185, 148, 151, 152, 248, 212, 184, 191, 214, 229, 168, 37, 5, 109, 67, 5, 161, 255, 120, 209, 68, 243, 12, 147, 21, 73, 167, 24, 191, 209, 0, 39, 2, 17, 0, 0, 0, 3, 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