Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6854255fa2b64008b538ec03d3d2a5c7a3e4c0d953a269413ec18470d4c1cbc3

Tx prefix hash: 74db938491e818622eed59ce8828c0a0f7ec7c4919ae9626ba2cca716e5995e3
Tx public key: 8514c2b01c83f39bc731185e7a35124824b803c717aaace6a3ad972715ee967e
Timestamp: 1581515995 Timestamp [UCT]: 2020-02-12 13:59:55 Age [y:d:h:m:s]: 05:021:21:40:24
Block: 63528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168401 RingCT/type: yes/0
Extra: 018514c2b01c83f39bc731185e7a35124824b803c717aaace6a3ad972715ee967e021100000001724f989b000000000000000000

1 output(s) for total of 378.012514140000 dcy

stealth address amount amount idx
00: f9b342d80ae5ca09086dd4d0df7c159ddbf3a99ef18d8b00338910de5973ab22 378.012514140000 117096 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": 63538, "vin": [ { "gen": { "height": 63528 } } ], "vout": [ { "amount": 378012514140, "target": { "key": "f9b342d80ae5ca09086dd4d0df7c159ddbf3a99ef18d8b00338910de5973ab22" } } ], "extra": [ 1, 133, 20, 194, 176, 28, 131, 243, 155, 199, 49, 24, 94, 122, 53, 18, 72, 36, 184, 3, 199, 23, 170, 172, 230, 163, 173, 151, 39, 21, 238, 150, 126, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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