Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9aa0a0898e197b225e4672e6c833f1ebe0608a9ff06015aece154c42e2956e

Tx prefix hash: f7a48eb843c0000d277c076df001aa6e7e97bbdbc5eb7505c8df3aa3d2b92f41
Tx public key: cd535e92db7ebd7f62515a86c7fcaa7468a560eeb85e3dd95fb30158a4463e36
Timestamp: 1581703335 Timestamp [UCT]: 2020-02-14 18:02:15 Age [y:d:h:m:s]: 04:363:16:00:20
Block: 65217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151641 RingCT/type: yes/0
Extra: 01cd535e92db7ebd7f62515a86c7fcaa7468a560eeb85e3dd95fb30158a4463e3602110000000212c4732d000000000000000000

1 output(s) for total of 373.172658790000 dcy

stealth address amount amount idx
00: c5c6f2fd1d2b1e56c04587a619e585c6de8336b47e8a4ba1a1a4c7901ab74c14 373.172658790000 120232 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": 65227, "vin": [ { "gen": { "height": 65217 } } ], "vout": [ { "amount": 373172658790, "target": { "key": "c5c6f2fd1d2b1e56c04587a619e585c6de8336b47e8a4ba1a1a4c7901ab74c14" } } ], "extra": [ 1, 205, 83, 94, 146, 219, 126, 189, 127, 98, 81, 90, 134, 199, 252, 170, 116, 104, 165, 96, 238, 184, 94, 61, 217, 95, 179, 1, 88, 164, 70, 62, 54, 2, 17, 0, 0, 0, 2, 18, 196, 115, 45, 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