Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 069f06e22d339dc9dcf9b519ef4f8828e8af84146b005800b3de8589600ff178

Tx prefix hash: a031e0d611bebca825632da87e4d417af7f62525e00dd4f9dbbf60be37c7538d
Tx public key: 69541c27b32bce61680abeb2329bfc782f6c83f1badc1ef8b5d153ea13aeaeb2
Timestamp: 1738522513 Timestamp [UCT]: 2025-02-02 18:55:13 Age [y:d:h:m:s]: 00:363:17:00:44
Block: 1210677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257630 RingCT/type: yes/0
Extra: 0169541c27b32bce61680abeb2329bfc782f6c83f1badc1ef8b5d153ea13aeaeb20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0181750ecf46d5f4ad202e5d0a78db4c01470c9cc181505544a8592d5a5ccc36 0.600000000000 1697430 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": 1210687, "vin": [ { "gen": { "height": 1210677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0181750ecf46d5f4ad202e5d0a78db4c01470c9cc181505544a8592d5a5ccc36" } } ], "extra": [ 1, 105, 84, 28, 39, 179, 43, 206, 97, 104, 10, 190, 178, 50, 155, 252, 120, 47, 108, 131, 241, 186, 220, 30, 248, 181, 209, 83, 234, 19, 174, 174, 178, 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