Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0332f8370f152279fb70eaf1e8bf4dcad775f2115d7af2d5e09c42445ead8347

Tx prefix hash: 201cfbf0504c75c3f051d4d0e14dae12b4af13d0dc78cc245081020bf7393c7d
Tx public key: ac545896d4dc9d0e6608bfa9fe227da1260c76e0d95c4b684ea3e595a20da1ca
Timestamp: 1719938374 Timestamp [UCT]: 2024-07-02 16:39:34 Age [y:d:h:m:s]: 00:173:13:53:19
Block: 1057050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124241 RingCT/type: yes/0
Extra: 01ac545896d4dc9d0e6608bfa9fe227da1260c76e0d95c4b684ea3e595a20da1ca0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b4bac43448994c2361619bb9eff77772e6d6ff7b8610dbcd6bdc178d6fe12b 0.600000000000 1527479 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": 1057060, "vin": [ { "gen": { "height": 1057050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b4bac43448994c2361619bb9eff77772e6d6ff7b8610dbcd6bdc178d6fe12b" } } ], "extra": [ 1, 172, 84, 88, 150, 212, 220, 157, 14, 102, 8, 191, 169, 254, 34, 125, 161, 38, 12, 118, 224, 217, 92, 75, 104, 78, 163, 229, 149, 162, 13, 161, 202, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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