Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e4196ca1d40f1fb3795075398f5ef48cbbeb9bfbdc1917450f9808e5d89a884

Tx prefix hash: c705c3574d66245df28c1903d084bc2faa064e06798dcd3c37b633d830f51676
Tx public key: df6441931cc9325226f2a54bb8b6ec563359a3d31569f5f4644d2f35842ba1ae
Timestamp: 1724337230 Timestamp [UCT]: 2024-08-22 14:33:50 Age [y:d:h:m:s]: 00:098:00:21:04
Block: 1093526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70106 RingCT/type: yes/0
Extra: 01df6441931cc9325226f2a54bb8b6ec563359a3d31569f5f4644d2f35842ba1ae021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1df24d425f090d039e654f3b0f68a7a98a6dfbbead76d66840d9bfb4da6b841 0.600000000000 1568487 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": 1093536, "vin": [ { "gen": { "height": 1093526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1df24d425f090d039e654f3b0f68a7a98a6dfbbead76d66840d9bfb4da6b841" } } ], "extra": [ 1, 223, 100, 65, 147, 28, 201, 50, 82, 38, 242, 165, 75, 184, 182, 236, 86, 51, 89, 163, 211, 21, 105, 245, 244, 100, 77, 47, 53, 132, 43, 161, 174, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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