Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c5206fe1e7857e33c6402c259a63128752ffcd84cd17d3e5bfce7cee4fb5b2

Tx prefix hash: 022385de08a6e7681e949bc96987ffee3d18b8dcbbfcc7129fcde79d8043f504
Tx public key: ffb3d9830143d25b0e3b5d772729980d5268f21a8d4854c74eb7c210239a91a2
Timestamp: 1735141776 Timestamp [UCT]: 2024-12-25 15:49:36 Age [y:d:h:m:s]: 00:097:16:22:27
Block: 1182970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69584 RingCT/type: yes/0
Extra: 01ffb3d9830143d25b0e3b5d772729980d5268f21a8d4854c74eb7c210239a91a20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ccfdab897d54d211c7e48adde4b3cec818f5a94ad543effda764371227e9b9f 0.600000000000 1669409 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": 1182980, "vin": [ { "gen": { "height": 1182970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ccfdab897d54d211c7e48adde4b3cec818f5a94ad543effda764371227e9b9f" } } ], "extra": [ 1, 255, 179, 217, 131, 1, 67, 210, 91, 14, 59, 93, 119, 39, 41, 152, 13, 82, 104, 242, 26, 141, 72, 84, 199, 78, 183, 194, 16, 35, 154, 145, 162, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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