Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa62563efc96b08f187de46e2257021c7531f61f0a643abd79cb63f4edaa770

Tx prefix hash: 65e2bd882ccf93d09e507ebf68c513a0738d02c51a941b18538f90da0a21e673
Tx public key: 77893b2ed077227b0bc209742466fdc5045d9aab1c409d427f3f11016f8b6b17
Timestamp: 1727378916 Timestamp [UCT]: 2024-09-26 19:28:36 Age [y:d:h:m:s]: 00:149:15:57:49
Block: 1118731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106735 RingCT/type: yes/0
Extra: 0177893b2ed077227b0bc209742466fdc5045d9aab1c409d427f3f11016f8b6b17021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfba4b840cf2dac4beecba214ade7cd2014d921db8e0e838f33305943dc6bd47 0.600000000000 1600026 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": 1118741, "vin": [ { "gen": { "height": 1118731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfba4b840cf2dac4beecba214ade7cd2014d921db8e0e838f33305943dc6bd47" } } ], "extra": [ 1, 119, 137, 59, 46, 208, 119, 34, 123, 11, 194, 9, 116, 36, 102, 253, 197, 4, 93, 154, 171, 28, 64, 157, 66, 127, 63, 17, 1, 111, 139, 107, 23, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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