Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa786a9b6a597e42f329427399dbd27a66f484b344587efc59b65c73e6afb5b

Tx prefix hash: 449426bdb3929827f5762c08d21f55ebc39d07207512d95ebb97734640a84f11
Tx public key: 1a8811387ad78bb32f727e09e5a838f10bf7622b7d3c77f4ac9f9406c77ce5ad
Timestamp: 1579938462 Timestamp [UCT]: 2020-01-25 07:47:42 Age [y:d:h:m:s]: 04:285:21:16:12
Block: 52343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094517 RingCT/type: yes/0
Extra: 011a8811387ad78bb32f727e09e5a838f10bf7622b7d3c77f4ac9f9406c77ce5ad021100000002dcee4b4d000000000000000000

1 output(s) for total of 411.686610023000 dcy

stealth address amount amount idx
00: ccd9ed464fd3996ae0953da1ad921bfc9e1db446d027f44db6db596f79b811d9 411.686610023000 97062 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": 52353, "vin": [ { "gen": { "height": 52343 } } ], "vout": [ { "amount": 411686610023, "target": { "key": "ccd9ed464fd3996ae0953da1ad921bfc9e1db446d027f44db6db596f79b811d9" } } ], "extra": [ 1, 26, 136, 17, 56, 122, 215, 139, 179, 47, 114, 126, 9, 229, 168, 56, 241, 11, 247, 98, 43, 125, 60, 119, 244, 172, 159, 148, 6, 199, 124, 229, 173, 2, 17, 0, 0, 0, 2, 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