Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce90c96bbbc204c2ac857c0095322071b7a6376be8b35ea676b920fa2e412306

Tx prefix hash: 792e795a8aacd1ed3cb7e81d93116401d0aa7935a4ef2b226b8762d33941603c
Tx public key: 0b1737bb4776aabf7b01500165cb1a236549b56345ec7adc9c395b246bab64a9
Timestamp: 1582978577 Timestamp [UCT]: 2020-02-29 12:16:17 Age [y:d:h:m:s]: 04:270:20:35:28
Block: 74083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087209 RingCT/type: yes/0
Extra: 010b1737bb4776aabf7b01500165cb1a236549b56345ec7adc9c395b246bab64a90211000001907adf42d3000000000000000000

1 output(s) for total of 348.765137393000 dcy

stealth address amount amount idx
00: eff6d14103d3c6aa90c392fe256decbc8647ecc54c3d6ac3708f5e657e35b993 348.765137393000 136913 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": 74093, "vin": [ { "gen": { "height": 74083 } } ], "vout": [ { "amount": 348765137393, "target": { "key": "eff6d14103d3c6aa90c392fe256decbc8647ecc54c3d6ac3708f5e657e35b993" } } ], "extra": [ 1, 11, 23, 55, 187, 71, 118, 170, 191, 123, 1, 80, 1, 101, 203, 26, 35, 101, 73, 181, 99, 69, 236, 122, 220, 156, 57, 91, 36, 107, 171, 100, 169, 2, 17, 0, 0, 1, 144, 122, 223, 66, 211, 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