Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479cbbc63745ede9d9a1b115a7cfba46ff5238be50bd4921960e945bc9e67fd3

Tx prefix hash: c40fc6471d6c4be8b147f6027de0c76ffd629dc052fdf78fe1d674d2d07e559b
Tx public key: cb92590c7a9ab21967995096bcb62e33ef43a6c3d4aeeb637a55821e91e61b2e
Timestamp: 1702723092 Timestamp [UCT]: 2023-12-16 10:38:12 Age [y:d:h:m:s]: 01:109:15:04:47
Block: 914322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339472 RingCT/type: yes/0
Extra: 01cb92590c7a9ab21967995096bcb62e33ef43a6c3d4aeeb637a55821e91e61b2e02110000000f75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30557266a1b28d9dd6ddaa2f2eb41e82362aef67e6b0731131174467066fd795 0.600000000000 1371634 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": 914332, "vin": [ { "gen": { "height": 914322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30557266a1b28d9dd6ddaa2f2eb41e82362aef67e6b0731131174467066fd795" } } ], "extra": [ 1, 203, 146, 89, 12, 122, 154, 178, 25, 103, 153, 80, 150, 188, 182, 46, 51, 239, 67, 166, 195, 212, 174, 235, 99, 122, 85, 130, 30, 145, 230, 27, 46, 2, 17, 0, 0, 0, 15, 117, 227, 240, 233, 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