Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d535ddfd87effb3c58b8c6346010fe9777078bb5dcde982619e5bb24dad970

Tx prefix hash: cdf7aa9b1f03e3ef899cee0ee1a3d0671c03d1b39fad58e3ee70ca21ea133500
Tx public key: defe6756ed496bb9aa95613a50789a9f63fe7e6af1f4fe6bd9a169d645af5d30
Timestamp: 1695925509 Timestamp [UCT]: 2023-09-28 18:25:09 Age [y:d:h:m:s]: 01:263:19:45:51
Block: 858168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449528 RingCT/type: yes/0
Extra: 01defe6756ed496bb9aa95613a50789a9f63fe7e6af1f4fe6bd9a169d645af5d300211000000024b8f5122000000000000000000

1 output(s) for total of 0.880102426000 dcy

stealth address amount amount idx
00: ea4c45aece0d4bfbe34d56a9dddc8d412f0c6876cb285fa810cc035eb175646e 0.880102426000 1312334 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": 858178, "vin": [ { "gen": { "height": 858168 } } ], "vout": [ { "amount": 880102426, "target": { "key": "ea4c45aece0d4bfbe34d56a9dddc8d412f0c6876cb285fa810cc035eb175646e" } } ], "extra": [ 1, 222, 254, 103, 86, 237, 73, 107, 185, 170, 149, 97, 58, 80, 120, 154, 159, 99, 254, 126, 106, 241, 244, 254, 107, 217, 161, 105, 214, 69, 175, 93, 48, 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