Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a02110f1e1bffbfc9acfca9bb58a9cc5aedf2a2f671095562ae4549972af7db3

Tx prefix hash: d02cf9d9ec64e600ec6db4896ed47c589c5af7ecc378fa3c0486f0e09ebe99d8
Tx public key: cee92cb79d1d089393d2e8c2949c0db256378f47da1b782ed1b1a099410100b1
Timestamp: 1762629278 Timestamp [UCT]: 2025-11-08 19:14:38 Age [y:d:h:m:s]: 00:019:11:37:28
Block: 1407848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13952 RingCT/type: yes/0
Extra: 01cee92cb79d1d089393d2e8c2949c0db256378f47da1b782ed1b1a099410100b1021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f8ead594ae6f83f51c925d26fcacdc4e02fc1b7733541993bc5cdbdb724ee0d 0.600000000000 1896273 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": 1407858, "vin": [ { "gen": { "height": 1407848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f8ead594ae6f83f51c925d26fcacdc4e02fc1b7733541993bc5cdbdb724ee0d" } } ], "extra": [ 1, 206, 233, 44, 183, 157, 29, 8, 147, 147, 210, 232, 194, 148, 156, 13, 178, 86, 55, 143, 71, 218, 27, 120, 46, 209, 177, 160, 153, 65, 1, 0, 177, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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