Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5984b2f45016daee0d1c862a79c19c29b82774f1e1ff48523415954bbefe82b2

Tx prefix hash: 682d754ce1451b87b84c5a025988f3e9023b0389569ba09ab74e0bdbf2e9920f
Tx public key: fea761dc78eaad2838a993b34465026553c9768d785668f876d9f851d7f4afb4
Timestamp: 1580268741 Timestamp [UCT]: 2020-01-29 03:32:21 Age [y:d:h:m:s]: 04:333:05:04:44
Block: 54810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128665 RingCT/type: yes/0
Extra: 01fea761dc78eaad2838a993b34465026553c9768d785668f876d9f851d7f4afb4021100000001dcee4b4d000000000000000000

1 output(s) for total of 404.010398509000 dcy

stealth address amount amount idx
00: d1d40a12720a6ac20a7ca7876923872ff7caa717857764ea6fa4d0ed0bbf8aed 404.010398509000 101304 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": 54820, "vin": [ { "gen": { "height": 54810 } } ], "vout": [ { "amount": 404010398509, "target": { "key": "d1d40a12720a6ac20a7ca7876923872ff7caa717857764ea6fa4d0ed0bbf8aed" } } ], "extra": [ 1, 254, 167, 97, 220, 120, 234, 173, 40, 56, 169, 147, 179, 68, 101, 2, 101, 83, 201, 118, 141, 120, 86, 104, 248, 118, 217, 248, 81, 215, 244, 175, 180, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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