Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af329c3d9b11eeeaa04983e0595aa25b2904435b12467b6c00e422870401fa88

Tx prefix hash: 8c6edbe57d6a656e7fcb05a6c010350c3225776a6f24f2c71b4a21a8618262c7
Tx public key: e8713034564a26cf37b6462d783ecd8b38dc79f2c506e98d3214553e10741d92
Timestamp: 1708499867 Timestamp [UCT]: 2024-02-21 07:17:47 Age [y:d:h:m:s]: 01:042:19:11:51
Block: 962219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291596 RingCT/type: yes/0
Extra: 01e8713034564a26cf37b6462d783ecd8b38dc79f2c506e98d3214553e10741d920211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bf5a9ceb63ece7ffa84d812fd03ab217fdd80dc36cb619ab2420f323578c956 0.600000000000 1421844 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": 962229, "vin": [ { "gen": { "height": 962219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf5a9ceb63ece7ffa84d812fd03ab217fdd80dc36cb619ab2420f323578c956" } } ], "extra": [ 1, 232, 113, 48, 52, 86, 74, 38, 207, 55, 182, 70, 45, 120, 62, 205, 139, 56, 220, 121, 242, 197, 6, 233, 141, 50, 20, 85, 62, 16, 116, 29, 146, 2, 17, 0, 0, 0, 2, 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