Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf78be2d7d131b7f6054b72468c2af53a6648afabf0a47720b948f353056305f

Tx prefix hash: df31084f81b744bfcfcc86ae9ac1153fcd81edbe332af4d6b7e219d854b12e70
Tx public key: c622f6aff011cbec227b38008146bf352c4c76176f376b017b4dc1b6a242a6a9
Timestamp: 1735433164 Timestamp [UCT]: 2024-12-29 00:46:04 Age [y:d:h:m:s]: 00:102:02:51:46
Block: 1185369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72785 RingCT/type: yes/0
Extra: 01c622f6aff011cbec227b38008146bf352c4c76176f376b017b4dc1b6a242a6a90211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aefcffc2b9b37e0f9b1d4fec883a27cd856b0fd17e83abb57561d153bd317ee2 0.600000000000 1671836 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": 1185379, "vin": [ { "gen": { "height": 1185369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aefcffc2b9b37e0f9b1d4fec883a27cd856b0fd17e83abb57561d153bd317ee2" } } ], "extra": [ 1, 198, 34, 246, 175, 240, 17, 203, 236, 34, 123, 56, 0, 129, 70, 191, 53, 44, 76, 118, 23, 111, 55, 107, 1, 123, 77, 193, 182, 162, 66, 166, 169, 2, 17, 0, 0, 0, 8, 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