Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1fea49875a64f57e93aec508f86681a5515207db61795be7041d3f1683c684a

Tx prefix hash: 7cfbb4ea79fad3af56c457d1e90508f97eb156c246a6bf061e8cfe8f7536460b
Tx public key: 1970e53d01cb18b635f43cb2b4d55ff83735c9f8dbafeb54cd54c8defd326975
Timestamp: 1581825442 Timestamp [UCT]: 2020-02-16 03:57:22 Age [y:d:h:m:s]: 04:277:01:42:27
Block: 66174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090017 RingCT/type: yes/0
Extra: 011970e53d01cb18b635f43cb2b4d55ff83735c9f8dbafeb54cd54c8defd32697502110000000156c366d3000000000000000000

1 output(s) for total of 370.490864178000 dcy

stealth address amount amount idx
00: 7610bebb7190a4b71ad5cf2db336d3dd230be3b182c537c624da0c9e74a85c9d 370.490864178000 121835 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": 66184, "vin": [ { "gen": { "height": 66174 } } ], "vout": [ { "amount": 370490864178, "target": { "key": "7610bebb7190a4b71ad5cf2db336d3dd230be3b182c537c624da0c9e74a85c9d" } } ], "extra": [ 1, 25, 112, 229, 61, 1, 203, 24, 182, 53, 244, 60, 178, 180, 213, 95, 248, 55, 53, 201, 248, 219, 175, 235, 84, 205, 84, 200, 222, 253, 50, 105, 117, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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