Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 292087333ffe3d7c80610802f5e8121835349383f789878d32cae2d9f6054a54

Tx prefix hash: cba21191d2ebbb92e3a88ba8c5387a60f26988b0ec0bf286baebfc67281bc1af
Tx public key: 056553de0ec793993f1d2da091aa5183b44d5f8d8d2e67a83226f450094ca257
Timestamp: 1714797092 Timestamp [UCT]: 2024-05-04 04:31:32 Age [y:d:h:m:s]: 00:341:18:34:32
Block: 1014424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244306 RingCT/type: yes/0
Extra: 01056553de0ec793993f1d2da091aa5183b44d5f8d8d2e67a83226f450094ca25702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ad5efea4e0ef0c086bfcc213eefcd5501d6adb934bd7f091d69932ef593f81 0.600000000000 1477513 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": 1014434, "vin": [ { "gen": { "height": 1014424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ad5efea4e0ef0c086bfcc213eefcd5501d6adb934bd7f091d69932ef593f81" } } ], "extra": [ 1, 5, 101, 83, 222, 14, 199, 147, 153, 63, 29, 45, 160, 145, 170, 81, 131, 180, 77, 95, 141, 141, 46, 103, 168, 50, 38, 244, 80, 9, 76, 162, 87, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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