Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b0fab6251bbc9eb7993dfb5615d2843a3876cd4d5eec1e7fc70739a8a87c82

Tx prefix hash: 7cdf40cbabb013de58aff554cee6947669b93abd87c2cf11f486ac13e8cc67a8
Tx public key: b47788bd28e2dd333c4ec43120e3c7cab5fa12dd92c5d9be50a94c26877d3bee
Timestamp: 1713842868 Timestamp [UCT]: 2024-04-23 03:27:48 Age [y:d:h:m:s]: 01:191:06:10:33
Block: 1006510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395338 RingCT/type: yes/0
Extra: 01b47788bd28e2dd333c4ec43120e3c7cab5fa12dd92c5d9be50a94c26877d3bee0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6e8df74603addad1d2aa6f2dff467152286eab5efaabbc5592ad53f61f8d962 0.600000000000 1467564 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": 1006520, "vin": [ { "gen": { "height": 1006510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6e8df74603addad1d2aa6f2dff467152286eab5efaabbc5592ad53f61f8d962" } } ], "extra": [ 1, 180, 119, 136, 189, 40, 226, 221, 51, 60, 78, 196, 49, 32, 227, 199, 202, 181, 250, 18, 221, 146, 197, 217, 190, 80, 169, 76, 38, 135, 125, 59, 238, 2, 17, 0, 0, 0, 1, 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