Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bedfadd0f7e966fd5fa6e76dd86d20c9d24fd3dd3c7f019e7af019d0afed1015

Tx prefix hash: 464050eee0e3ca65346b9fa213d65f0de24dae9d1f987b419998d181c96c1bc9
Tx public key: 185663dd1ca10ffb35adcd29d1cf26637af4d8b7e451f2d83e37f046a14488c8
Timestamp: 1686029130 Timestamp [UCT]: 2023-06-06 05:25:30 Age [y:d:h:m:s]: 02:180:15:20:49
Block: 776161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648922 RingCT/type: yes/0
Extra: 01185663dd1ca10ffb35adcd29d1cf26637af4d8b7e451f2d83e37f046a14488c80211000000024b8f5122000000000000000000

1 output(s) for total of 1.645343470000 dcy

stealth address amount amount idx
00: 511cdb24583cb8d0d138ab306d48e8b50c3cb39d52f0e58cdaaa6f76dffd9ef6 1.645343470000 1225698 of 0

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": 776171, "vin": [ { "gen": { "height": 776161 } } ], "vout": [ { "amount": 1645343470, "target": { "key": "511cdb24583cb8d0d138ab306d48e8b50c3cb39d52f0e58cdaaa6f76dffd9ef6" } } ], "extra": [ 1, 24, 86, 99, 221, 28, 161, 15, 251, 53, 173, 205, 41, 209, 207, 38, 99, 122, 244, 216, 183, 228, 81, 242, 216, 62, 55, 240, 70, 161, 68, 136, 200, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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