Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c3ddb06f64f7fbcb33d9b3583622a9a9e4d70f42a939aa1cc615d76c24f134

Tx prefix hash: 53790fc59c6a8356677ada5d3521e46bf1fcbb5e37e9815312eb40fbf135f5d2
Tx public key: 680df4de562afda5cbc23b1cedbe5f39593c1dc5ab9d6ab790d4361cf57a74d9
Timestamp: 1578318180 Timestamp [UCT]: 2020-01-06 13:43:00 Age [y:d:h:m:s]: 05:299:22:18:04
Block: 39702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1362211 RingCT/type: yes/0
Extra: 01680df4de562afda5cbc23b1cedbe5f39593c1dc5ab9d6ab790d4361cf57a74d90211000005c749b77a3d000000000000000000

1 output(s) for total of 453.415772013000 dcy

stealth address amount amount idx
00: 123f0cd1b69d50da491858b33f2f6990384842fce136be45e65b84063fc237ff 453.415772013000 68866 of 0

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": 39712, "vin": [ { "gen": { "height": 39702 } } ], "vout": [ { "amount": 453415772013, "target": { "key": "123f0cd1b69d50da491858b33f2f6990384842fce136be45e65b84063fc237ff" } } ], "extra": [ 1, 104, 13, 244, 222, 86, 42, 253, 165, 203, 194, 59, 28, 237, 190, 95, 57, 89, 60, 29, 197, 171, 157, 106, 183, 144, 212, 54, 28, 245, 122, 116, 217, 2, 17, 0, 0, 5, 199, 73, 183, 122, 61, 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