Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6cce7e88874e08e0c11b8d35098ccc1e7aa456a626f27b12c09cfba022aeaac

Tx prefix hash: 7dcac0d1440fa7ea4a24f945926149d2324a375a4c10eacb5e4d3b4249f669e5
Tx public key: 78fe45dace08ad065868ce633e5dd5423c3e55dc1bc4424e6dcf1eeba82f72cd
Timestamp: 1709055277 Timestamp [UCT]: 2024-02-27 17:34:37 Age [y:d:h:m:s]: 00:363:18:43:20
Block: 966832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260090 RingCT/type: yes/0
Extra: 0178fe45dace08ad065868ce633e5dd5423c3e55dc1bc4424e6dcf1eeba82f72cd02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15860b67a9825f8ee1f9c8e051e786c7d90b1337483e307c5cbaf3f92b403b47 0.600000000000 1426603 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": 966842, "vin": [ { "gen": { "height": 966832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15860b67a9825f8ee1f9c8e051e786c7d90b1337483e307c5cbaf3f92b403b47" } } ], "extra": [ 1, 120, 254, 69, 218, 206, 8, 173, 6, 88, 104, 206, 99, 62, 93, 213, 66, 60, 62, 85, 220, 27, 196, 66, 78, 109, 207, 30, 235, 168, 47, 114, 205, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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