Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 078e15a0ecb351c2551e247faa6a34f456c3802e73bdb18bd0295b6d9384a9fc

Tx prefix hash: 4c0f45340bab8b8a5aec01fe92d050860359a505ab7fff28db2fb9c6e8dc9698
Tx public key: 70d46810ccb910bfeb893a2dce043405c59658956d447dc3e8f7df450d3894bc
Timestamp: 1577554013 Timestamp [UCT]: 2019-12-28 17:26:53 Age [y:d:h:m:s]: 05:312:14:42:14
Block: 33651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1371007 RingCT/type: yes/0
Extra: 0170d46810ccb910bfeb893a2dce043405c59658956d447dc3e8f7df450d3894bc021100000015ac34bf9e000000000000000000

1 output(s) for total of 474.789520556000 dcy

stealth address amount amount idx
00: 640c55bac3c111ef60bc760a9aa099c5511e87256a6577833366b4881dc81a97 474.789520556000 56426 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": 33661, "vin": [ { "gen": { "height": 33651 } } ], "vout": [ { "amount": 474789520556, "target": { "key": "640c55bac3c111ef60bc760a9aa099c5511e87256a6577833366b4881dc81a97" } } ], "extra": [ 1, 112, 212, 104, 16, 204, 185, 16, 191, 235, 137, 58, 45, 206, 4, 52, 5, 197, 150, 88, 149, 109, 68, 125, 195, 232, 247, 223, 69, 13, 56, 148, 188, 2, 17, 0, 0, 0, 21, 172, 52, 191, 158, 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