Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85a6db4c9764e7491c743c23401d8fd3216fbfe66216110cc170bda0c1bc1236

Tx prefix hash: e9b2220f57505e53440fa61c2c256b300b045c55a99c157c1213caec26d3eb8f
Tx public key: 0c193da9b0cd8b42272ae8210a0c8dfc8981bb0e51b5238e81431579868974eb
Timestamp: 1718616766 Timestamp [UCT]: 2024-06-17 09:32:46 Age [y:d:h:m:s]: 00:219:03:31:46
Block: 1046087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156786 RingCT/type: yes/0
Extra: 010c193da9b0cd8b42272ae8210a0c8dfc8981bb0e51b5238e81431579868974eb0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a897c6073f0c238765a16b83ae0ab09bd54071ae277669366c84bda4d68f6bf 0.600000000000 1515846 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": 1046097, "vin": [ { "gen": { "height": 1046087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a897c6073f0c238765a16b83ae0ab09bd54071ae277669366c84bda4d68f6bf" } } ], "extra": [ 1, 12, 25, 61, 169, 176, 205, 139, 66, 39, 42, 232, 33, 10, 12, 141, 252, 137, 129, 187, 14, 81, 181, 35, 142, 129, 67, 21, 121, 134, 137, 116, 235, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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