Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969a5cc849a457df6e8d0194e9c9814fb5ae4107727e119743da444d1e43bae5

Tx prefix hash: 67654bd7516be927cffac9a6f90e85639e7ab5a6280fec5719a9ccafa7ebfcc1
Tx public key: 75434902c8ae2d9b0e3cbd0aecf2a14afd58d6a70459a6cea13df6c7f9d3679e
Timestamp: 1716414477 Timestamp [UCT]: 2024-05-22 21:47:57 Age [y:d:h:m:s]: 00:310:15:13:10
Block: 1027828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222018 RingCT/type: yes/0
Extra: 0175434902c8ae2d9b0e3cbd0aecf2a14afd58d6a70459a6cea13df6c7f9d3679e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d56f8a3fc217e2d832957d19528814ebfecc3dc589eefa02c0862b9bc679d18 0.600000000000 1495661 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": 1027838, "vin": [ { "gen": { "height": 1027828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d56f8a3fc217e2d832957d19528814ebfecc3dc589eefa02c0862b9bc679d18" } } ], "extra": [ 1, 117, 67, 73, 2, 200, 174, 45, 155, 14, 60, 189, 10, 236, 242, 161, 74, 253, 88, 214, 167, 4, 89, 166, 206, 161, 61, 246, 199, 249, 211, 103, 158, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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