Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fde314e4ec33c0f691fee31bcb11017b21b81b6d67f622f62c8f33c7beca04e

Tx prefix hash: d569ef3ff953d8ac7dbaf241b7e243661f5d4367b34dd3929ffba40bb20f94e4
Tx public key: 63733d1902da9e715f80949ea78b9ac56b3122b215e1d3673f7cecf20e5d0f7e
Timestamp: 1577119801 Timestamp [UCT]: 2019-12-23 16:50:01 Age [y:d:h:m:s]: 05:046:04:48:47
Block: 30034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182872 RingCT/type: yes/0
Extra: 0163733d1902da9e715f80949ea78b9ac56b3122b215e1d3673f7cecf20e5d0f7e0211000000204ac5aa02000000000000000000

1 output(s) for total of 488.074089219000 dcy

stealth address amount amount idx
00: 8f0a6bfaaf1c401cf37c0b5b7d3e366309fac4ef29213c398dec4f7a445960a1 488.074089219000 49580 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": 30044, "vin": [ { "gen": { "height": 30034 } } ], "vout": [ { "amount": 488074089219, "target": { "key": "8f0a6bfaaf1c401cf37c0b5b7d3e366309fac4ef29213c398dec4f7a445960a1" } } ], "extra": [ 1, 99, 115, 61, 25, 2, 218, 158, 113, 95, 128, 148, 158, 167, 139, 154, 197, 107, 49, 34, 178, 21, 225, 211, 103, 63, 124, 236, 242, 14, 93, 15, 126, 2, 17, 0, 0, 0, 32, 74, 197, 170, 2, 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