Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534caddb66f7948c4ca1f2e5d05ca2866ed5b667255d5d124ea7cc1da651012b

Tx prefix hash: 454bb57a11142851b94e0df4b36ac05a14b7d9d5c17355e45c5e97501d629a32
Tx public key: bd45366b9a09604f678b8856c7606a6f0f2bd78b2061c9d3647d7bac149c175d
Timestamp: 1574725954 Timestamp [UCT]: 2019-11-25 23:52:34 Age [y:d:h:m:s]: 05:073:13:04:47
Block: 17520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195133 RingCT/type: yes/0
Extra: 01bd45366b9a09604f678b8856c7606a6f0f2bd78b2061c9d3647d7bac149c175d021100000001f95225a5000000000000000000

1 output(s) for total of 536.969783386000 dcy

stealth address amount amount idx
00: 648bf1c0094a7de83aafa6f798e66bd55d0d6010894d54fa13b233986232c978 536.969783386000 25581 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": 17530, "vin": [ { "gen": { "height": 17520 } } ], "vout": [ { "amount": 536969783386, "target": { "key": "648bf1c0094a7de83aafa6f798e66bd55d0d6010894d54fa13b233986232c978" } } ], "extra": [ 1, 189, 69, 54, 107, 154, 9, 96, 79, 103, 139, 136, 86, 199, 96, 106, 111, 15, 43, 215, 139, 32, 97, 201, 211, 100, 125, 123, 172, 20, 156, 23, 93, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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